Skip to main content
Glama

list_entities

Read-onlyIdempotent

Lists entities of a specified type with limit and offset controls, enabling you to browse available records by entity category.

Instructions

List entities of a specific type.

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": {
      "entity_type": "<entity_type>"
    },
    "name": "list_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
entity_typeYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds only the type-filtering idea and does not explain ordering, pagination behavior, error behavior for unknown types, or any other operational context beyond the schema and annotations.

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?

The definition is a single front-loaded sentence with no wasted wording. It is efficient, though extremely bare, with under-specification handled in the contextual completeness dimension rather than as verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with a required type parameter, pagination parameters, and many sibling list/search tools, the description is too thin. The presence of an output schema and rich annotations reduces some burden, but the description still omits entity-type domain guidance, pagination expectations, and sibling routing.

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%, so the description needs to carry parameter meaning. It only implies that entity_type is a type filter and says nothing about limit or offset, leaving pagination semantics to be inferred from property names and defaults.

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?

The description states a clear verb and resource: list entities. It also narrows the scope to a specific type. It does not distinguish this tool from nearby alternatives such as semantic_search_entities or get_entity.

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 gives no explicit when-to-use guidance, prerequisites, or alternatives. It only restates the basic capability of listing entities by type, leaving the agent to infer when this is preferable to semantic search or get_entity.

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