Skip to main content
Glama
Sign In
GitPin

GitPin

by shmindmaster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

pin.search_docs

Read-onlyIdempotent

Search for documentation candidates in Git repositories. Locate relevant docs for factual assertions, then validate with proof and verification loops.

Instructions

Find documentation candidates (not claims). Before any factual assertion call pin.prove or pin.prove_set, then pin.verify.

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": "pin.search_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
repositoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the key behavioral context that results are 'documentation candidates (not claims)' — i.e., they are unverified and require subsequent prove/verify steps. This goes beyond the annotations and informs the agent about result reliability.

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 two concise sentences with no filler. It front-loads the core purpose and immediately adds a critical usage constraint. Every sentence earns its place.

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

Completeness3/5

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

Given there is no output schema, the description should explain what the tool returns. It says 'documentation candidates' but does not specify the result format, pagination, or how to interpret results. The repository parameter is also unexplained. Overall, the description is useful but incomplete for a search tool with no output schema.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It does not explain 'query' or 'repository' at all. While 'query' is self-explanatory, 'repository' is ambiguous (repository name? path? filter scope?) and the description adds no clarification.

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 clearly states the tool's purpose: 'Find documentation candidates (not claims).' This uses a specific verb and resource, and the parenthetical distinguishes it from claim-verification tools like pin.prove and pin.verify. It also differentiates from pin.search_code by focusing on documentation.

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?

The description provides clear workflow guidance: 'Before any factual assertion call pin.prove or pin.prove_set, then pin.verify.' This tells when to use this tool in a larger pipeline. However, it does not explicitly mention alternatives like pin.search_code or state when not to use this tool, so it falls short of a 5.

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

Deploy Server

Other Tools