Skip to main content
Glama

ide_project_items

Read-only

List project elements as the IDE sees them, with optional filtering by artifact type such as Class, Table, Form, or Edt.

Instructions

List the elements of a project as the IDE sees them, optionally filtered by artifact type such as Class, Table, Form or Edt.

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": {
      "path": "<path>"
    },
    "name": "ide_project_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
rootNo
typeNo

Output Schema

NameRequiredDescriptionDefault
okYes
errorNo
itemsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that results are scoped to a project and reflect the IDE's view, but says nothing about result ordering, pagination, or what happens when the path does not resolve to a project.

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?

A single front-loaded sentence with the core action first and the optional filter second. No filler, though it is arguably too terse for a tool with undocumented parameters.

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?

An output schema exists, so return values need not be explained. However, with three undescribed parameters and no mention of the path/root distinction, the definition is only partially complete for a project-scoped query tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description must carry the load. It only illuminates the 'type' parameter with concrete examples (Class, Table, Form, Edt); 'path' and 'root' receive no explanation of format or relationship, leaving two of three parameters undocumented anywhere.

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: listing a project's elements as the IDE sees them, with an optional type filter. It is clearly distinguishable from ide_references or ide_search, though it never names a sibling to route against.

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 phrase 'optionally filtered by artifact type' implies how to narrow results, but there is no explicit guidance on when to use this versus ide_search, project_inspect, or ide_definition. Usage is implied rather than directed.

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