Skip to main content
Glama
Sign In
astrograph

astrograph

by Thaylo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

generate_ignore

Idempotent

Creates a default .astrographignore file with sensible exclusions, so only relevant code gets indexed for duplicate detection.

Instructions

Auto-generate .astrographignore with reasonable defaults for excluding files from indexing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generate_ignore"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.6

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already indicate idempotent (idempotentHint=true) and non-destructive (destructiveHint=false) behavior. The description adds the context of generating 'reasonable defaults' but does not clarify whether the tool overwrites an existing .astrographignore or preserves custom entries. The description does not contradict 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?

The description is a single sentence, front-loaded with the verb 'Auto-generate' and the resource '.astrographignore'. It is succinct with no wasted words.

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 the tool's simplicity (no params, no output schema) and the presence of annotations, the description adequately conveys the core behavior. However, it lacks guidance on when to use this tool over alternatives like 'write' or 'edit', and it does not mention the fate of an existing .astrographignore file, leaving some context incomplete.

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 tool has zero parameters, and the schema confirms this with 100% coverage. There is no need for parameter descriptions. The baseline for zero parameters is 4, and the description appropriately does not invent parameter details.

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 action ('Auto-generate') and target resource ('.astrographignore') with a specific purpose ('excluding files from indexing'). This distinguishes it from sibling tools like 'write' and 'edit' which are generic file operations.

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 when a default ignore file is needed, but it does not explicitly state when to use this tool versus alternatives such as manually creating the file via 'write' or 'edit'. No exclusions or alternative recommendations are provided.

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