Skip to main content
Glama
najaeda

naja-scope

by najaeda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

find

Read-onlyIdempotent

Search case-sensitive object names across a loaded design using a glob pattern when the exact path is unknown. Returns typed descriptors with pagination.

Instructions

Search case-sensitive object names across the loaded design with a glob. Use this when an exact path is unknown; use resolve once a path is known or get_hierarchy to browse structure. A dot in pattern switches matching to full hierarchical paths. Returns typed descriptors in matches plus count, has_more, and an opaque next_cursor for pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoRestrict results to one design-object kind, or any.any
limitNoPage size; defaults to 50 and is capped at 200.
cursorNoOpaque next_cursor from the previous response; omit for the first page.
patternYesCase-sensitive glob; include a dot to match full hierarchical paths.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.9
    • addedInput schema / properties / cursor / description
      Added value: +"Opaque next_cursor from the previous response; omit for the first page."
    • addedInput schema / properties / kind / description
      Added value: +"Restrict results to one design-object kind, or any."
    • addedInput schema / properties / kind / enum
      Added value: +[
+  "instance",
+  "net",
+  "port",
+  "module",
+  "any"
+]
    • addedInput schema / properties / limit / description
      Added value: +"Page size; defaults to 50 and is capped at 200."
    • addedInput schema / properties / pattern / description
      Added value: +"Case-sensitive glob; include a dot to match full hierarchical paths."
  2. First observedv0.1.8

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that by disclosing the glob-dot path-switching rule and the return/pagination shape (matches with typed descriptors, count, has_more, next_cursor) in the absence of an output schema. It does not discuss result-ordering or cost, so it stops short of a 5.

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?

Four tight sentences, front-loaded with the core action before usage guidance and return shape. Every sentence carries distinct information (purpose, routing, return structure) with no filler.

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?

For a read-only search tool, the definition covers purpose, sibling routing, glob semantics, and the return/pagination contract. With annotations carrying the safety profile and no output schema, an agent has everything needed to call it correctly on the first try.

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 all four parameters are already documented in the schema (kind enum, limit default/cap, cursor origin, pattern dot rule). The description restates the pattern-dot behavior and explains pagination flow, but adds no syntax or constraints the schema lacks, so the baseline of 3 applies.

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?

States a specific verb (search), resource (case-sensitive object names in the loaded design) and mechanism (glob), which is far more than the vague name 'find' conveys. It also names two siblings (resolve, get_hierarchy) and the conditions that select them, letting an agent distinguish it without opening a schema.

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?

"Use this when an exact path is unknown; use resolve once a path is known or get_hierarchy to browse structure" gives explicit when-to-use, when-not, and named alternatives. Nothing about tool selection is left to inference.

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