Skip to main content
Glama

Babelii-Diofis Account

Cari penjelasan resmi

search_knowledge
Read-onlyIdempotent

Retrieve approved business explanations permitted to this identity. Never use indexed prose as current price, balance or device status.

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": {
      "query": "<query>"
    },
    "name": "search_knowledge"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and retry semantics are covered. The description adds information the annotations cannot carry: results are vetted ("approved") and permission-scoped to the caller's identity, and the prose is explicitly non-authoritative for live values — an important limitation that shapes how an agent should cite results.

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 sentences, front-loaded with the capability and followed by the guardrail — no filler. The phrase "indexed prose" is slightly jargon-like and could be stated more plainly, but the structure is efficient.

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?

An output schema exists, so return shape need not be described, and annotations fully cover safety profile. Combined with the authority caveat in the description, an agent has enough to call this correctly; the missing piece is how this differs from the conversational ask_abel sibling.

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 coverage is 0% for the single required "query" parameter, so the description carries the burden of explaining it, and it says nothing about query syntax, natural-language vs keyword expectations, or matching behavior. The parameter name is self-evident enough that this is not fatal, but a one-clause note on what the query should contain would materially help.

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 pairs a specific verb ("Retrieve") with a scoped resource ("approved business explanations permitted to this identity"), so an agent knows this is an identity-scoped knowledge lookup rather than a live-data tool. It does not, however, distinguish itself from siblings such as ask_abel or discover_babelii, which appear to occupy adjacent territory.

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 second sentence gives an explicit when-NOT-to-use constraint for the returned content (do not treat it as current price, balance or device status), which is genuinely useful. But there is no positive statement of when to call this tool, and no alternative is named for price/balance/device-status questions, leaving the agent to infer the routing.

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