get_bot_summaryRetrieve the built-in AI summary of a MeetStream meeting by providing its bot ID. Use this tool to get the meeting recap generated by MeetStream without external LLM processing.
MeetStream's built-in AI summary of the meeting (no external LLM needed).
| Name | Required | Description | Default |
|---|---|---|---|
| bot_id | Yes |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds context that the summary is generated by MeetStream's built-in AI rather than an external LLM, which is useful. It does not disclose return format, latency, or whether the summary is precomputed, but no contradiction exists.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, tightly written sentence that front-loads the core purpose and adds one meaningful qualifier. Every word earns its place; there is no filler or redundant restatement of the tool name.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter read-only getter, the description names the resource and scope adequately. However, with no output schema, it does not indicate what the response contains, and it does not clarify bot_id provenance or route the agent among the summary/transcript/detail sibling tools. It is minimally viable but has clear gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and the description never mentions bot_id. While 'bot_id' is somewhat self-explanatory, the description adds no meaning about what the ID represents, where to obtain it, or how it relates to sibling tools like create_bot. The description fails to compensate for the low schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource: getting MeetStream's built-in AI meeting summary, and adds a useful differentiator with 'no external LLM needed.' It does not explicitly distinguish this from sibling tools like get_transcript or get_bot_detail, but the core purpose is clear.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'built-in AI summary' and 'no external LLM needed' implies this is the tool to use when you want MeetStream's own summary rather than raw transcript or external processing. However, it never names alternatives or states when not to use this tool, leaving usage guidance mostly implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.