Skip to main content
Glama

gflow_character_show

Show one saved Flow CHARACTER entity by id or by exact display name. Read-only, spends no credits. On flow.google.com, returns the character's entity_id, display_name, voice, personality, workflow_ids and thumbnail_media_id.

Instructions

Show one saved Flow CHARACTER entity by id or by exact display name. Read-only, spends no credits. On flow.google.com, returns the character's entity_id, display_name, voice, personality, workflow_ids and thumbnail_media_id. Exactly one of entity_id or name is required; ambiguous names fail. Drives a browser.

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": {
      "project": "<project>"
    },
    "name": "gflow_character_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
profileNodefault
projectYes
entity_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does meaningful work: it declares read-only behavior, states that no credits are spent, discloses that it drives a browser, and warns that ambiguous names fail. The only gap is that it does not mention authentication or what happens if the id/name is not found.

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?

Four short sentences, front-loaded with purpose and safety, then the constraint and behavior. The enumeration of returned fields (entity_id, display_name, voice, personality, workflow_ids, thumbnail_media_id) is somewhat redundant given an output schema exists, which is the only wasted space.

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?

The output schema covers return values and the description covers cost, side effects, and key-selection rules, so the core call path is well specified. Completeness is docked only for the unexplained required "project" and the "profile" parameter, which matter at call time with 0% schema coverage.

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 0%, so the description must compensate, and it does explain the entity_id/name mutual-exclusivity and the exact-match requirement for names. But the required "project" parameter and the "profile" parameter receive no explanation anywhere, leaving half the parameters undocumented.

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?

"Show one saved Flow CHARACTER entity by id or by exact display name" gives a specific verb (show), a specific resource (character entity), and a scope (exactly one), which implicitly separates it from gflow_character_list. It stops short of naming the list sibling as the alternative, so an agent must infer the contrast rather than read it.

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 description gives a real usage rule for the lookup keys ("Exactly one of entity_id or name is required; ambiguous names fail"), which is genuinely helpful for invocation. However it never says when to reach for this tool versus gflow_character_list or gflow_character_voices, so the alternative-selection guidance is only implied by the singular scope.

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