Skip to main content
Glama

get_checkin_answers

Read-only

Get a check-in's questions + latest answers. PHOTO-type answers are resolved to fetchable image URLs — pass those into get_client_images to actually view them.

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": {
      "checkInId": "<checkInId>"
    },
    "name": "get_checkin_answers"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkInIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

readOnlyHint=true and openWorldHint=false already declare the safety and locality profile, so the description's added value must come from elsewhere. It does disclose one real behavioral trait: PHOTO-type answers are transformed into fetchable image URLs rather than raw data, which an agent could not infer from the schema. Beyond that it says nothing about ordering of answers, recency semantics of 'latest', or empty-result behavior.

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

Conciseness5/5

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

Two short sentences, purpose front-loaded, and the follow-up instruction placed immediately after the behavior it depends on. No filler or restated title.

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?

There is no output schema, so the description usefully explains the one non-obvious aspect of the return value (photo answers become image URLs) and the next step to render them. The remaining gap is the unstructured checkInId parameter, which neither schema nor description explains.

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 0% and the single required parameter checkInId is undocumented in both schema and description. The phrase 'a check-in's' implies the ID selects the check-in, but format (UUID? numeric?) and sourcing are left unstated, so the description adds only marginal meaning beyond the property 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?

States a specific verb and resource: 'Get a check-in's questions + latest answers', which is concrete enough to distinguish it from get_checkin (metadata) or get_checkin_logs. It doesn't explicitly name a sibling to contrast with, so it stops short of the top score.

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?

Provides one concrete follow-up rule — PHOTO answers must be passed into get_client_images to be viewed — which is genuinely useful workflow guidance. However, it offers no guidance on when to call this versus get_checkin, get_checkin_logs, or other check-in tools, so the when-to-use question is only partly answered.

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.