Skip to main content
Glama

Metis · Software Engineer — Search Code Repository

search_code_repository

Search code repository to find reusable scripts, functions, and dataset variables matching your query. Optionally restrict by project or language.

Instructions

Search the Code Repository for prior code, variables and treatments.

Finds reusable scripts/functions, dataset variables and cleaning steps that
match a query — e.g. "Poisson model offset" or "catastrophic expenditure".

Args:
    query: What you're looking for.
    project_id: Restrict to one project. Optional.
    language: Restrict to a language (r, python, …). Optional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
languageNo
project_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must disclose all behavioral traits. It only describes the search action and does not mention any side effects, rate limits, pagination, or limitations. The read-only nature is implied but not confirmed.

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?

The description is concise and front-loaded with the main purpose. The separate 'Args' section for parameters is well-structured. Every sentence contributes meaning, though the examples could be slightly more integrated.

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?

The description covers the basic functionality and parameter semantics. Since an output schema is present, the lack of return value explanation is acceptable. However, it does not address edge cases like empty results or multiple matches, leaving some gaps for a simple search tool.

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?

The input schema has 0% description coverage, but the 'Args' section in the description adds meaningful descriptions for all three parameters (e.g., 'What you're looking for.' for query). These add value beyond the schema's titles and types.

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 it searches the Code Repository for code, variables, and treatments, with concrete examples ('Poisson model offset'). It distinguishes from sibling search tools by specifying the unique resource (Code Repository).

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 through its purpose and examples but does not explicitly state when to use this tool over alternatives like search_fulltext or search_literature. No when-not or exclusion criteria are provided.

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/SVerITG/Metis'

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