Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

list_people_profiles_at_page

Lists CRM contacts in the workspace for a specific page, enabling paginated retrieval of additional people profiles.

Instructions

Lists CRM contacts in the workspace for one specified page. This tool is paginated, more entries can thus be retrieved.

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_people_profiles_at_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoThe page number to list people profiles at.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose one real behavioral trait — the tool returns a single page and repeated calls retrieve more entries — but says nothing about page size, ordering, permissions, or behavior past the final page.

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 with the core purpose front-loaded. The second sentence's phrasing ("more entries can thus be retrieved") is slightly awkward but not wasteful, and no padding is present.

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?

For a simple one-parameter read tool with no output schema, the description covers purpose and pagination but omits what a page actually yields — whether a total count or next-page indicator is returned — which is the key unknown for an agent driving a pagination loop.

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 coverage is 100% and the single `page` parameter is fully documented with a default and minimum, so the baseline is 3. The description adds only that the page is "one specified page," which restates rather than extends the schema's meaning.

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 ("Lists CRM contacts") and clarifies that 'people profiles' means CRM contacts, which helps bridge the tool name to meaning. It does not distinguish itself from siblings such as search_people_profiles or get_people_profile, so an agent must infer the difference.

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?

Usage is only implied by "This tool is paginated, more entries can thus be retrieved." There is no explicit when-to-use guidance, no statement that this is for full enumeration versus the search tool for filtered lookup, and no note about when to stop paging.

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