Skip to main content
Glama

List directors and employees

crunch_list_persons
Read-only

List directors and employees linked to a business on a given date and return their IDs for DIRECTORS_EXPENSES payments and expense lines.

Instructions

List the people (directors and employees) linked to the business on a date. Use their IDs as the person for DIRECTORS_EXPENSES payments and as the employee on expense lines.

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": "crunch_list_persons"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate the people were in post (YYYY-MM-DD; default today)
roleNoOnly people with this role, as Crunch names it (for example DIRECTOR)
limitNoMaximum number of items
fieldsNoKeep only these fields (dot paths, such as supplier.companyName)
searchNoCase-insensitive substring match on any value

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.7/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 one genuinely useful behavioral fact not in the annotations: the result set is time-scoped — only people 'in post' on the given date. It says nothing about the anomaly flagged by idempotentHint=false (results changing as staff join/leave) or about limit/pagination behavior.

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?

Two short sentences, front-loaded with the core action and resource, then the downstream consumption note. Every clause carries information; no filler or restatement of the title.

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?

With zero required parameters, full schema coverage, and no output schema, the definition covers what an agent needs to call it and what the output is useful for. A brief note on what the records contain (IDs plus names/roles) would close the remaining gap left by the absent output schema.

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 is already documented, which sets the baseline at 3. The description reinforces the meaning of 'date' as 'in post on that date' but adds no syntax, defaults, or semantics for role, limit, fields, or search beyond the schema.

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 (List) and a precisely scoped resource (people — directors and employees — linked to the business), plus the temporal qualifier 'on a date'. No sibling tool lists people, so the resource itself makes it distinguishable from the other crunch_list_* tools.

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 description explains what the returned IDs are for ('use their IDs as the person for DIRECTORS_EXPENSES payments and as the employee on expense lines'), which implies when to call it, but it never states when not to use it or how to choose between this and, say, crunch_get_company_details for people data. Usage is implied rather than prescribed.

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