Skip to main content
Glama

Get Character

get_character
Read-onlyIdempotent

[read] One character with all its fields (character_bio, character_note, character_appearances and character_variables (the filled look details as [{key, value, text}]), voice, AI account, storage account, character_assets, character_main_asset_id, character_reference_asset_id).

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": {
      "character_uuid": "<character_uuid>"
    },
    "name": "get_character"
  }
}

Input Schema

NameRequiredDescriptionDefault
character_uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world behavior, so the description only needs to add context beyond safety. It does list the returned field set, including the nested character_variables format, but it does not say what happens when the UUID is absent, whether fields can be null, or anything about errors.

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

Conciseness4/5

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

It is a single front-loaded sentence with no filler, and the field enumeration is useful rather than redundant. The long parenthetical is dense but still structurally clear.

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

Completeness4/5

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

For a simple one-parameter read tool with no output schema, the description supplies a useful inventory of returned fields and annotations cover the safety profile. The main omission is parameter-level guidance, but the tool remains easy to invoke correctly from the schema.

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?

The single parameter character_uuid has 0% schema description coverage, and the description never mentions the parameter, its expected format, or how to obtain it. For a low-coverage schema the description should compensate, but it adds no meaning beyond the parameter name.

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 identifies a read operation returning exactly one character and enumerates the fields included, making it clearly distinct from list_characters and get_character_variables. It is slightly weakened by not using an explicit verb such as 'retrieve', but the [read] tag and field list make the purpose clear.

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

Usage Guidelines3/5

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

The phrase 'one character with all its fields' implies this is the full-detail lookup for a single character, which distinguishes it implicitly from list_characters and get_character_variables. However, it never states when to prefer this over those siblings or any exclusions, so the guidance is only implied.

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.