Skip to main content
Glama

Prompt & Co. — Shared Operational Memory for AI Agents

List known entities

list_entities
Read-only

List the businesses, places, products, apps and workflows that observations can be filed under. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
afterNoCursor from a previous call's next value

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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, and the description usefully adds that calls are free and that the set is a closed, known catalog of entity types. It says nothing about result size, whether the full list is returned, or how the cursor paginates, which the schema only partially covers.

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?

Two short sentences, front-loaded with the verb and resource, with the entity taxonomy and the cost note each earning their place. Nothing is padded or repetitive.

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 single-parameter, read-only enumeration with annotations covering side effects, the description gives enough to call it correctly. Only a note on result shape or whether the catalog is small enough to fetch wholesale is missing, and no output schema exists to cover that.

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

Parameters5/5

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

Zero required parameters and a single optional cursor documented at 100% schema coverage; the description needs to add nothing more for an agent to call this correctly.

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?

Uses a specific verb ("List") with a concrete resource, and spells out what counts as an entity (businesses, places, products, apps, workflows) plus its relationship to observations. It does not explicitly name a sibling or contrast itself with one, so it stops short of 5.

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?

Usage is only implied: the phrase "that observations can be filed under" suggests this is the lookup to run before filing an observation, and "Free" signals no cost. There is no explicit when-to-use, when-not-to-use, or pointer to search_experiences/submit_observation as alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.