Skip to main content
Glama

读取知识库条目

get_entry
Read-only

按条目 id 取回内容(Markdown)。长条目分段返回:正文前面的说明写明共几段和各段标题,用 part 参数读其余各段。

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": {
      "id": "<id>"
    },
    "name": "get_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
partNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already cover the read-only and non-open-world properties, so the description does not need to. It discloses the nontrivial behavior that long entries are chunked and the number of parts is discoverable from the returned preamble. It says nothing about behavior when an id is missing or a part is out of range.

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, with the core retrieval action front-loaded and the segmentation caveat following. Every clause carries information about how to call the tool.

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 two-parameter read tool with no output schema, the retrieval and segmentation model is adequately conveyed, including the return format. The main omissions are the default behavior for part and the response when the id is not found.

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?

The input schema has 0% description coverage, so the description must carry parameter meaning. It explains that id identifies the entry and that part selects one of the segmented chunks, which is real added value, but it never states the default when part is omitted or what a chunk contains apart from the overall Markdown format. This compensates partially, not fully, for the empty schema documentation.

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?

The description states a specific verb and resource combination: '按条目 id 取回内容(Markdown)'. Combined with the explicit 'by id' retrieval scope, it clearly distinguishes this tool from the sibling list_entries, which lists entries rather than fetching one.

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?

It explains the practical workflow for long entries: read the preamble to learn how many parts there are and each part's title, then use the part parameter for the rest. It does not state when to prefer this tool over list_entries or first finding an id, but the conditions for using the part parameter are clear.

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.

Resources