Skip to main content
Glama

Search agentic-os methodology

search_methodology
Read-onlyIdempotent

Search across agentic-os governance, SDLC pipeline, and QE blueprint documentation using full-text AND matching to find relevant documents.

Instructions

Full-text search over the agentic-os governance, agentic-sdlc pipeline, and agentic-qe blueprint documentation. Use it first whenever you do not already hold a document URI, then pass a result uri to get_document for the full text. Matching is AND, not OR — every term must appear — and terms match at word starts, so "gate" finds "gates" and "gating" but "ate" finds neither. It searches markdown only: role presets are JSON and never appear here, so use list_presets for those. Read-only and idempotent; searches the server's own bundled corpus, never the network or your repository.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results, best-scoring first (1-25).
queryYesSearch terms, e.g. "write scope enforcement". Every term must appear in a document for it to match, so two or three distinctive words find more than a full sentence does. Runs of fewer than two alphanumeric characters are ignored, and punctuation is not searchable.
pluginNoRestrict results to one plugin: agentic-os (governance), agentic-sdlc (the SDLC pipeline), or agentic-qe (QE blueprints). Omit to search all three, which is usually right unless you already know the area.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYesMatching documents, best first. Empty when nothing matched — a normal result, not an error; broaden the query or drop the plugin filter.
Behavior5/5

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

Discloses matching behavior (AND, word starts) and data scope (server's bundled corpus, never network/repository). Annotations already provide readOnlyHint and idempotentHint, but description adds context on what is and isn't searched, beyond annotations.

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?

Single paragraph with front-loaded purpose. Each sentence adds unique information (usage order, matching behavior, scope, idempotency). No wasted words.

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?

Complete for a search tool with 3 parameters (100% schema coverage), output schema existing, and annotations present. Covers when to use, how matching works, what is searched, and idempotency.

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 has 100% coverage, so baseline is 3. Description adds extra value: explains query matching, limit ordering, and plugin meanings. Without this, agent might not understand plugin enum values or matching rules.

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?

Clearly states the tool is for full-text search over agentic-os documentation, identifying the verb 'search' and specific resource. Distinguishes from siblings by explicitly mentioning alternatives: get_document for full text and list_presets for role presets.

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 says 'Use it first whenever you do not already hold a document URI' and instructs to pass a result URI to get_document. Also explains matching semantics (AND, word starts) and scope (markdown only, not JSON presets), differentiating from list_presets.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jarroslav/agentic-os'

If you have feedback or need assistance with the MCP directory API, please join our Discord server