Skip to main content
Glama

List Jeb Units

list_jeb_units
Idempotent

Lists project units by stable path and type with wildcard filtering, parent-scope restriction, and pagination so you can discover and page through available units.

Instructions

List project units by stable unit path and type, with optional wildcard filter, parent restriction, and pagination. The engine caps pages at 100 units; a full page reports partial coverage because more units may exist. Read-only.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
countNoMaximum results to return; the engine protocol caps pages at 100
indexNoZero-based index of the first result to return
filterNoWildcard filter matched against unit paths; '*' allowed
parent_unit_pathNoRestrict results to descendants of this unit path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior1/5

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

The description asserts "Read-only", but the annotations declare readOnlyHint=false, a direct conflict about whether this operation is safe/non-mutating. The one genuinely useful disclosure (engine caps pages at 100 and a full page signals partial coverage) does not offset a false safety claim in a field agents rely on. This is an annotation contradiction.

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?

Compact and front-loaded: capability, options, then the pagination caveat, with no filler. The closing "Read-only." sentence is short but actively misleading, which is a structural defect rather than a length problem.

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 zero-required-parameter listing tool with full schema coverage and annotations, it covers the main operational pitfall (truncated pages implying incomplete results). It never describes the returned unit shape, which matters slightly since there is no output schema, and its safety statement is wrong.

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 every parameter (filter, parent_unit_path, index, count) is already documented in the schema, including the 100 cap on count. The description only restates those concepts at a high level and adds no syntax or semantics beyond the schema.

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 ("List project units") plus the identity keys returned ("stable unit path and type"), and enumerates the narrowing options. It does not name or contrast any sibling (e.g., other list_* tools in this catalog), so an agent must infer which listing tool applies.

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?

The description explains what knobs exist (wildcard filter, parent restriction, pagination) but gives no when-to-use or when-not-to-use guidance and no prerequisites. Nothing tells the agent which tool to choose when several listing tools could satisfy a request.

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