Skip to main content
Glama

Coline

List scheduling links

list_scheduling_links
Read-onlyIdempotent

Lists the person's scheduling links, the pages where others book time with them.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>"
    },
    "name": "list_scheduling_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety and determinism profile is fully covered structurally. The description adds only the clarification that these are the person's own links (a scope statement), and says nothing about pagination, result size, or ordering — though the output schema carries return shape.

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?

One short sentence, front-loaded with the action and resource, plus a compact gloss that earns its place by disambiguating an unfamiliar domain term. No filler.

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?

A simple one-parameter read tool with an output schema, so return values need not be explained and annotations cover the safety profile. The only real gap is that the description is silent on the required workspace scoping, which the schema happens to cover.

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?

There is a single required parameter (workspace) with 100% schema description coverage, so the schema already explains the slug format and its source from workspaces.list. The description never mentions the workspace requirement or that it is mandatory; baseline 3 is appropriate when the schema does the work.

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?

"Lists the person's scheduling links" gives a specific verb (Lists) and resource (scheduling links), and the appositive "the pages where others book time with them" defines the resource for agents unfamiliar with the term. It does not explicitly distinguish itself from get_scheduling_link or create_scheduling_link, but the plural list framing makes the scope readable.

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: an agent can infer this is the enumeration call versus the get/create/update/delete siblings. There is no explicit when-to-use or when-not-to-use statement, and no mention that the result is scoped to the authenticated person rather than other users.

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.

Resources