Skip to main content
Glama

Show what the AI was sent

sent_to_ai
Read-only

Lists AI conversations newest first or returns every response sent in a chosen conversation in order, so you can verify what the AI saw.

Instructions

Show what the AI was sent (for 'what did you see?'). With no conversation_id, list the conversations, newest first; with one, every response sent in it, in order.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sent_to_ai"
  }
}

Input Schema

NameRequiredDescriptionDefault
conversation_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds genuinely useful behavioral detail: the no-argument case lists conversations newest-first, while supplying an id returns every response in order. It says nothing about volume, limits, or whether conversations are scoped to the current account.

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?

Two short sentences, front-loaded with the core purpose and immediately followed by the two-mode behavior. No filler; the parenthetical trigger phrase earns its place by anchoring user intent.

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?

For a single optional-parameter read tool with annotations covering the safety profile and no output schema, the definition covers purpose, both modes, and ordering. Only minor gaps remain (result size, account scoping), which are unlikely to cause a wrong invocation.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry the parameter, and it does completely: absent conversation_id means a conversation list, present conversation_id means all responses in that one conversation, returned in order. That is a full specification of the parameter's effect, including its default branch.

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 gives a specific verb and resource ('Show what the AI was sent') and ties it to a concrete user intent ('what did you see?'), so the agent knows exactly what data this returns. It does not name or contrast with the closest sibling (ai_log), so the boundary between the two must be inferred from names alone.

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?

Usage is grounded in a real trigger phrase ('for what did you see?') and the description explains which mode applies depending on whether conversation_id is supplied. It stops short of stating when NOT to use it or naming an alternative such as ai_log.

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