Skip to main content
Glama
Sign In

MangroveAI

by io.github.MangroveTechnologies
OverviewDiscussionsAdmin

kb_glossary_get

Read-onlyIdempotent

Return the KB glossary entry for an explicitly requested glossary definition or exact glossary term. No preliminary graph call is required for a glossary request. For a general question such as what RSI means, why it behaves that way, or which indicators complement it, start with query_knowledge op=ask. Exact lookup is case-insensitive and may return partial matches. Answer from the returned definition when sufficient; do not routinely follow it with graph or document searches.

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": {
      "term": "<term>"
    },
    "name": "kb_glossary_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesThe term to look up, case-insensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered; the description adds real context beyond that — no preliminary graph call is needed, matching is fuzzy ("may return partial matches"), and follow-up searches are discouraged. It stops short of describing the returned shape or empty-result behavior, so it is strong but not exhaustive.

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?

Four compact sentences, each doing distinct work: purpose, pre-call expectation, alternative routing, and post-call handling. The most important constraint (this is for explicit/exact requests) is front-loaded with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A single required parameter, full schema coverage, and clear annotations mean very little needs saying — yet the description still covers the pre-call assumption and the follow-up posture. No output schema exists, but the definition's guidance on answering from the returned definition compensates.

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 100% and the schema already documents term as case-insensitive, so the description's case-insensitivity note largely repeats structured data. The one genuinely additive detail is that lookups may return partial matches, which affects how the agent interprets a hit, but that is a single increment.

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?

States a specific verb and resource ("Return the KB glossary entry") plus the scope ("explicitly requested glossary definition or exact glossary term"), which cleanly separates it from kb_search and query_knowledge. An agent can identify the tool without inspecting the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes general conceptual questions such as "what RSI means" to query_knowledge op=ask, and reserves this tool for exact-term requests. It also gives post-call guidance ("answer from the returned definition when sufficient; do not routinely follow it with graph or document searches"), covering both when-to-use and when-not-to-chain.

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

All MangroveAI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources