Skip to main content
Glama

One character

get_character
Read-onlyIdempotent

One of your characters or products: name, kind ("person" for a character, "object" for a product), the brands it belongs to (brandIds), whether its identity sheet (what keeps the face consistent in every image and video) is ready, being made or failed, whether it has a voice, its connected platforms and a profile picture link that expires in an hour.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "characterId": "<characterId>"
    },
    "name": "get_character"
  }
}

Input Schema

NameRequiredDescriptionDefault
characterIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description does add genuine behavioral context the annotations cannot: the profile picture link expires after an hour, and the identity-sheet field has three explicit states (ready / being made / failed) with a plain-language definition of what an identity sheet is. What it omits is what happens on a bad ID or whether a not-ready identity sheet blocks other tools.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence with the resource stated up front, which is good front-loading, but the field enumeration is delivered as a chain of nested parentheticals that makes it hard to scan. The content is dense and mostly earns its place, though the inline glosses could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully documents the returned shape — kinds, brandIds, identity-sheet status, voice presence, platforms, expiring avatar URL — which is the right thing to spend words on. However, for a lookup-by-ID tool it never tells the agent where the ID comes from or how failures surface, leaving a real gap in calling it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the sole parameter `characterId` is described nowhere in the schema. The description likewise never mentions the ID argument, its accepted format, or where to obtain one (e.g. from `list_characters`), so it fails to compensate for the total coverage gap on a required parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description makes clear this returns a single character or product entity and enumerates its constituent fields (name, kind, brands, identity sheet state, voice, platforms, avatar link). It lacks an explicit verb like "retrieve" and never names `list_characters` as the plural alternative, but the singular scope and the field list distinguish it well enough from sibling list tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this rather than `list_characters` or `list_brands`, no prerequisite that the caller must already hold a characterId, and no note on error behavior for an unknown or foreign ID. Usage is only implied by the phrase "One of your characters".

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources