Unicode Character Grounding Data

Overview

Unicode Character Lookup works by analyzing Unicode characters or codepoints to retrieve detailed information including decimal/hex codepoint, UTF-16 encoding, category (letter, number, emoji, etc.), and emoji names from the Unicode emoji database.

Live Test Unicode Character Grounding Data Source →

The tool

Once your client is connected to the VerveContext server, this appears in its tool list as UnicodeCharacterGroundingData. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

Tool call

{
  "name": "UnicodeCharacterGroundingData",
  "arguments": {}
}

Connecting

One server URL covers every source in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp"
    }
  }
}

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

Argument	Type	Description
`character`Optional	string	The Unicode character to lookup. Supply either character or codepoint.
`codepoint`Optional	string	The Unicode codepoint in hex (e.g., '1F44B' or 'U+1F44B'). Supply either character or codepoint.

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

Result

{
  "status": "ok",
  "error": null,
  "data": {
    "character": "�",
    "codepoint": "U+D83D",
    "decimal": 55357,
    "hex": "D83D",
    "utf16": "\\uD83D",
    "category": "Control",
    "name": null
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`character`	string	`�`	The Unicode character being looked up
`codepoint`	string	`U+D83D`	The Unicode codepoint in U+ notation format
`decimal`	number	`55357`	The decimal representation of the character codepoint
`hex`	string	`D83D`	The hexadecimal representation of the character codepoint
`utf16`	string	`\uD83D`	The UTF-16 encoding representation of the character
`category`	string	`Control`	Unicode category classification (e.g., Control, Letter, Number)
`name`	object	`null`	The emoji name when the character is an emoji (e.g. "red heart"); null for other characters

Why ground on it

A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value in a shape you can check, which is the difference between an answer you can cite and one you have to hedge.

Point an evaluation at decimal: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

Status	What it means
`400` / `422`	The arguments did not validate. The message names the offending one.
`401`	The OAuth session is invalid or expired — reconnect the server.
`403`	Blocked by a key restriction or an IP allow-list. Never a bad identity.
`404`	This source is not part of VerveContext. Check the catalog.
`429`	Out of credits, or a brief rate limit. The message tells them apart.

A call costs 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Character Analysis: Analyze Unicode characters in text to understand their encoding, category, and properties
Emoji Information: Look up emoji names and Unicode information for emoji keyboards, pickers, or documentation
Debugging: Debug character encoding issues by examining Unicode properties and encodings of problematic characters
Documentation: Generate documentation about supported characters, emojis, or special symbols with detailed Unicode info

Other ways to use Unicode Character Grounding Data

Set up Unicode Character Grounding Data on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →

Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →