Skip to main content
Glama

get_client_images

Read-only

Fetch check-in photo(s) and return base64-encoded image data for visual analysis. Pass imageUrl(s) from get_checkin_answers's photoAnswers.

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": {
      "imageUrls": "<imageUrls>"
    },
    "name": "get_client_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageUrlsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered structurally; the description's real addition is disclosing that the result is base64-encoded image data, which matters because there is no output schema and the payload is heavy. It does not mention the 10-image cap, request cost, or failure behavior for unreachable URLs, so behavioral disclosure stays at an adequate level.

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 sentences, no filler, with the action and return type front-loaded and the input-provenance instruction second. Every clause earns its place.

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?

For a one-parameter read tool with annotations covering safety, the description covers purpose, input provenance, and return format well. Gaps remain around batch limits (maximum 10 URLs), partial failures, and payload size expectations, which are relevant for a base64 image tool with no output schema.

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

Parameters4/5

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

Schema description coverage is 0%, so the description carries the burden and does: it explains that imageUrls are the photoAnswers values from get_checkin_answers, giving the parameter real meaning beyond a bare string array. It omits the maxItems=10 and non-empty-string constraints that the schema encodes structurally but never explains.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (fetch check-in photo(s)) and adds the return shape (base64-encoded image data for visual analysis), which an agent cannot infer from the name alone. It also names where the input comes from, tying it to get_checkin_answers' photoAnswers rather than the many other get_client_* siblings that return text data.

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 explicit upstream guidance: pass imageUrls sourced from get_checkin_answers's photoAnswers, which effectively defines the prerequisite call sequence. It stops short of stating exclusions or what to do when photoAnswers is empty or contains more than the accepted maximum, so it is strong but not fully bidirectional.

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.