Skip to main content
Glama
Anou4r

superchat

by Anou4r
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

superchat_list_custom_attributes

Read-onlyIdempotent

List custom contact attributes with IDs, types, and allowed values. Use pagination cursors to navigate pages. Find attribute IDs before searching or updating.

Instructions

List one page of custom contact attributes with their IDs, types and allowed values. Look up an attribute ID here before searching by or updating that attribute.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoFetch the page after this cursor; pass pagination.next_cursor from a previous result.
limitNoNumber of records in this page, from 1 to 100. Defaults to 25; the tool never fetches later pages automatically.
beforeNoFetch the page before this cursor; pass pagination.previous_cursor from a previous result. Cannot be combined with after.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The description adds behavioral context beyond the annotations by specifying that only one page is returned and what fields are included. Since readOnlyHint, idempotentHint, and destructiveHint annotations already cover safety, the description need not repeat them. No contradiction exists.

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 sentences with no fluff. The core purpose is front-loaded, and the usage hint is separated cleanly. Every word earns its place.

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

Completeness5/5

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

For a simple read-only paginated list tool, the description is sufficient: it states what the tool returns, that it is paginated to one page, and when it should be consulted. Annotations and schema cover safety and parameters, so nothing essential is missing.

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 cursor and limit parameters are already fully explained in the schema. The description does not need to add parameter details; it receives the baseline score for not duplicating schema content.

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?

The description states a specific action ('List'), a specific resource ('custom contact attributes'), and the scope ('one page'), and also names the returned fields (IDs, types, allowed values). This clearly distinguishes the tool from the many get/list siblings in the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence gives practical usage guidance: use this tool before searching or updating an attribute to look up its ID. It does not explicitly name alternatives or when-not-to-use conditions, but the usage context is clear and actionable.

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