Skip to main content
Glama
getdomovoi

osnova

Official
by getdomovoi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

osnova_ground

Read-onlyIdempotent

Search a local repository by keyword or identifier to find definitions with exact file:line and signatures. Locates route registrations and handlers when you don't know where code lives.

Instructions

Search: find definitions by keyword or identifier. Each hit gives exact file:line, kind, definition span and signature, without source lines. Pass lean=false to inline the whole definition when it is 40 lines or shorter and an 8-line excerpt otherwise, or full=true to inline whole definitions. Start here when you do not know where code lives. A verb and path (GET /users) finds the route registration and its handler for Express, NestJS, Flask and FastAPI.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inNoRestrict to a file or directory path (repo-relative)
fullNoInline whole definitions instead of 8-line excerpts
leanNoDefault true: keep file:line, kind, definition span and signature without source; false inlines source; an explicit true overrides full
limitNoMaximum hits (default 8)
questionYesNatural-language or keyword query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations cover read-only, idempotent, non-destructive safety. The description adds output-format behavior: lean vs full inlining and defaults. It doesn't cover rate limits, auth, or failure modes, but for a read-only search this is adequate.

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 and output format, then parameter behavior. Some redundancy between the initial list and later detail, but overall tight and useful.

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 read-only search tool with full schema coverage and no output schema, this description covers purpose, output shape, parameter interactions, and a usage entry point. It lacks sibling differentiation, which is the main gap.

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%, so the schema already documents parameters. The description explains the interaction between lean and full (lean=false inlines if <=40 lines or an 8-line excerpt; full=true inlines whole), which adds value beyond schema descriptions.

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 it is a search tool that finds definitions by keyword or identifier, and adds specific behavior: it returns file:line, kind, definition span, and signature. The mention of route registration for frameworks distinguishes it from a generic text search.

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?

Tells the agent to start here when code location is unknown, which gives a clear use context. It doesn't explicitly compare to sibling tools like osnova_groundwork or osnova_outline, but the routing is strong.

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