Skip to main content
Glama

Coline

Show Code

show_code
Read-onlyIdempotent

Shows the crew's Code sessions inside the chat as Coline's Code cards, or one session, live while it runs.

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": {
      "workspace": "<workspace>"
    },
    "name": "show_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdNoShow this session.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
openYes
sessionsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral context by saying the cards appear 'inside the chat' and can show a session 'live while it runs,' but it does not clarify how live updates behave, whether the tool returns a rendered card versus structured data, or any limitations of the live view.

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?

The definition is a single front-loaded sentence with no wasted preamble. It is concise and readable, though the internal product phrasing 'Coline's Code cards' slightly reduces immediate clarity.

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?

The tool has full parameter documentation, annotations covering its safety profile, and an output schema, so the description does not need to explain return values. However, for a display-oriented tool with a live-update mode, the description omits important usage guidance and does not clarify how the live card view differs from the one-session view or from sibling retrieval tools.

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 description coverage is 100%, so both parameters are already documented in the schema. The description only loosely maps the optional sessionId by saying 'or one session' and does not mention the required workspace parameter, so it adds little meaning beyond what the schema provides. A baseline score of 3 is appropriate.

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 states a specific verb and resource: it shows the crew's Code sessions in the chat, optionally one session, rendered as Code cards. This is clearly a display/rendering tool, though it relies on the internal term 'Coline's Code cards' and does not explicitly distinguish itself from siblings like get_code_session or list_code_sessions.

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 explicit guidance on when to use this tool versus get_code_session, list_code_sessions, or get_code_diff. The phrase 'or one session' implies that passing a session ID narrows the view, but the description never states when that variant is appropriate or when the broader list view should be used instead.

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