Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

developer_search

Search indexed developer documentation. Searches indexed sources only; this operation never starts ingestion or contacts upstream sources.

Instructions

Search indexed developer documentation. Searches indexed sources only; this operation never starts ingestion or contacts upstream sources. The current ready source is go:docs and it covers only the 18 selected verified pages documented by developer-sources. Search matches Unicode-aware lexical terms and punctuation-bearing identifiers such as context.Context; passages retain byte/line locators into the indexed document. types accepts doc, readme, issue, and pull_request, but the current source supports only doc; unsupported values return 400. The version filter is not supported by the current unversioned source and returns 400. Continuation bodies contain only cursor and optional limit; their pages come from the frozen snapshot and do not repeat the search.

Input Schema

NameRequiredDescriptionDefault
requestYesSearch query or cursor-only continuation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so richly: it discloses matching semantics (Unicode-aware lexical, punctuation identifiers), locator retention, snapshot-based continuation, and explicit 400 behavior for unsupported `types` values and the unsupported `version` filter.

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?

Front-loaded with the core purpose, then dense constraint detail. Every sentence carries information, though the long single block is at the edge of being terse rather than tight.

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?

For a no-annotation, no-output-schema tool with a nested request object, the description covers source coverage, matching behavior, error behavior, and continuation shape — enough for an agent to call it correctly without guessing.

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 description coverage is high, so baseline is 3, but the description adds real semantics beyond the schema: which `types` values actually work today (only `doc`), that `version` is unsupported and errors, and that continuation bodies carry only `cursor` and optional `limit`.

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: 'Search indexed developer documentation.' It also draws a sharp line against ingestion-type behavior ('never starts ingestion or contacts upstream sources'), which an agent can use to separate it from source-management or crawl siblings.

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?

Gives clear context for when the tool applies (indexed sources only, current ready source is `go:docs` covering 18 verified pages) but stops short of naming an alternative sibling for cases where the search is not applicable.

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