Skip to main content
Glama

User Associations List

user_associations_list

Retrieve a paginated collection of the authenticated user's associations, passing sort, filter, and include options through query parameters.

Instructions

Get collection of associations of the authenticated user.

GET /user/associations

page_number/page_limit map to page[number]/page[limit]; query passes extra query parameters (sort, filter, q, include, fields[...]) through verbatim.

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

Input Schema

NameRequiredDescriptionDefault
queryNo
page_limitNo
page_numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must carry behavioral meaning. It discloses that this is a GET/read operation scoped to the authenticated user and explains pagination/query parameter mapping, but it does not cover response shape, pagination defaults, permissions, or error behavior.

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?

The description is short, front-loaded, and contains no unnecessary wording. Purpose, endpoint, and parameter mapping are presented efficiently.

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 simple list endpoint with no annotations or output schema, the description covers the core purpose, authentication scope, endpoint, and parameter behavior. It could say more about returned collection structure or pagination defaults, but it is sufficient for correct invocation.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must explain all three parameters. It does this well by mapping page_number/page_limit to page[number]/page[limit] and explaining that query passes through sort, filter, q, include, and fields parameters verbatim.

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 clearly states the verb and resource: get the collection of associations belonging to the authenticated user, with the exact endpoint. It does not explicitly distinguish this tool from any sibling, but the sibling list does not include a close alternative.

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 intended use is implied by 'Get collection of associations of the authenticated user' and the endpoint path. There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named.

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