Skip to main content
Glama

get_meeting_report_detail

按 report_id 取会议摘要详情(meta 含作者与正文摘要,长文按 4000 字截断)+ 原文链接。

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": {
      "report_id": "<report_id>"
    },
    "name": "get_meeting_report_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_idYessearch_meeting_reports 返回的 id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses that the response is a meta object containing author and body abstract, that long text is truncated at 4000 characters, and that an original-source link is included. This is genuine behavioral context an agent needs to avoid misreading truncated output as complete. It does not cover failure modes or permissions.

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?

One dense, front-loaded sentence with the primary action first and payload details in a trailing parenthetical. Nothing is wasted, though the closing '+ 原文链接' fragment is terse enough to feel like an afterthought.

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-parameter read tool with no output schema and no annotations, the description is nearly sufficient: it characterizes the returned payload, the truncation behavior, and the supplementary link. Only error/empty-result behavior and any access requirements are absent.

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% and there is a single required parameter, so the schema already documents the id fully. The description's '按 report_id' adds no format, range, or provenance detail beyond what the schema states, so the baseline 3 applies.

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: fetch the detail record for a meeting summary keyed by report_id, and names the two payload components (meta with author and abstract, plus the source link). It reads clearly as the single-item counterpart to search_meeting_reports, though it never says so explicitly in the description text itself.

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?

The description implies a detail-fetch pattern, and the parameter schema explicitly ties the id back to 'search_meeting_reports 返回的 id', which routes the agent correctly. However, neither text states when to call this versus re-querying search_meeting_reports, nor what to do if the id is unknown or stale.

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.