Skip to main content
Glama

find_type

Read-onlyIdempotent

Locate class, interface, struct, enum, and type definitions by name, returning file and line. Supports .* wildcards for partial matches in a codebase.

Instructions

Find class, interface, struct, enum and type definitions by name, with file and line.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
allNoList everything instead of stopping at 200 items.
nameYesType name; literal text with optional .* wildcards.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so safety is covered. The description adds that results are definition locations ('with file and line'), which is useful context. It omits the 200-item truncation behavior, which lives only in the schema's 'all' parameter.

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?

A single front-loaded sentence with no filler: verb, resource, covered kinds, and return payload in order of importance.

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 two-parameter lookup with full schema coverage and rich annotations, the description supplies what the schema cannot: what a hit looks like (file and line). The only gap is truncation/pagination behavior, which is partly recoverable from the 'all' parameter.

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 description coverage is 100%, so both 'name' (wildcards, minLength) and 'all' (bypass 200-item limit) are already documented. The description's 'by name' merely echoes the schema and does not explain wildcard syntax or the truncation default.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Find ... type definitions') and enumerates the kinds covered (class, interface, struct, enum), plus the return payload ('file and line'). This implicitly separates it from find_function/usages, though it never names a sibling to contrast against.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no alternative tool is named. The agent can infer that this is a name-based definition lookup, but nothing tells it when to prefer this over find_function, usages, or query.

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