Skip to main content
Glama
Sign In

mcp

by com.budgetpixel
OverviewDiscussionsAdmin

Get Character

get_character
Read-only

Use this to learn one character before casting it or using it elsewhere: its look word for word, personality, speaking style, backstory, directing notes, signature details and consistency rules, every picture with a download link (full size for the BudgetPixel influencers and the user's own characters, so they can be used with other tools too), the models a mention works on, and the terms for using an influencer. Use the profile to write prompts, captions and scripts in the character's own voice. Free.

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

Input Schema

NameRequiredDescriptionDefault
handleYesThe character's handle, with or without the @ (e.g. "barry"), from list_characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/non-destructive/closed-world, so the description is free to add the traits that actually matter here: cost ('Free'), the full inventory of returned data with no output schema to fall back on, and the availability constraint that full-size download links apply only to BudgetPixel influencers and the user's own characters. That is substantial disclosure beyond structured fields.

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?

Usage is front-loaded in the opening clause, then the return contents are listed. The middle sentence is a long run-on enumeration, but each item earns its place because no output schema exists to document the return payload.

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

Completeness5/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 carries the return-value burden and does so thoroughly — content of the profile, image availability tiers, model compatibility, influencer terms, and cost. Nothing an agent needs before calling this read-only tool is missing.

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

Parameters3/5

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

Schema coverage is 100% and the schema itself explains the single handle parameter, including the optional '@' and its source (list_characters). The description adds nothing further about the handle. Baseline 3 applies when the schema does all the work.

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?

States a specific verb and resource ('learn one character') and then enumerates exactly what that retrieval yields (look, personality, speaking style, backstory, images, model compatibility, usage terms). The scope word 'one' implicitly separates it from the list_characters sibling, but that alternative is never named, so the differentiation is left to inference.

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

Usage Guidelines4/5

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

Gives clear context for use: 'before casting it or using it elsewhere' and 'use the profile to write prompts, captions and scripts in the character's own voice.' There is no explicit when-not-to-use clause or named alternative (e.g. list_characters for browsing), so it stops short of full routing guidance.

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

All mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources