Skip to main content
Glama

Codethrift

Search Codethrift

search
Read-onlyIdempotent

Search Codethrift entries by name, description or tag. Each word is searched separately and results that match more words rank first. Returns each entry's owner/name (all from the reviewed commons shelf), description, tags and URLs.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
matchNotext: substring of name or description. tag: exact tag (topic).text
queryYesWords to look for, for example "tiff streak". Up to 5 words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare this is a read-only, idempotent, non-destructive operation. The description adds meaningful behavioral context by explaining per-word matching and relevance ranking, plus what fields are returned, though it omits pagination behavior.

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?

The description is three compact sentences, front-loaded with the core purpose and followed by ranking and return-value details. Every sentence adds useful information with no redundant wording.

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 simple search tool with no output schema and annotations covering safety, the description is nearly complete: it explains the matching model, ranking, and returned fields. The main gap is that it does not describe how the limit parameter affects results or whether pagination exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is moderate at 67%, and the description adds important semantic detail beyond the schema by explaining that each word is searched separately and results matching more words rank higher. It also clarifies that entries can be searched by name, description, or tag, though it does not describe the limit parameter.

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 states a specific verb and resource: searching Codethrift entries by name, description, or tag. It clearly explains the search scope and result ranking, but it does not explicitly distinguish this tool from siblings such as get_entry.

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 usage for finding entries by keywords, names, descriptions, or tags, but it gives no explicit when-to-use guidance or comparison to alternative tools. An agent can infer the general context, but not the boundary conditions for choosing this tool.

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