Skip to main content
Glama
Sign In
Shortcut MCP Server

Shortcut MCP Server

by ptamb3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Shortcut Member

get_member

Retrieve a Shortcut member's details by providing their UUID.

Instructions

Get a Shortcut member by UUID.

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": {
      "member_id": "<member_id>"
    },
    "name": "get_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
member_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states 'Get a Shortcut member by UUID' and adds no context about authentication, error handling, return format, or side effects. The read-only nature is implied by 'Get' but not explicitly disclosed.

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 a single sentence that conveys the essential purpose without any fluff or redundancy. It is highly concise and front-loaded.

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

Completeness2/5

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

For a tool with no output schema and no annotations, the description should explain what is returned or any special behavior. It does not mention the return value at all, and the dry_run parameter remains unexplained. The low complexity helps, but the gaps make it incomplete.

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

Parameters2/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 clarify parameters. It helps identify member_id as a UUID, but it does not explain the dry_run parameter at all. With two parameters and no schema descriptions, this leaves a significant gap.

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 clearly states the tool's action ('Get') and resource ('Shortcut member'), and specifies the lookup method ('by UUID'), which distinguishes it from list_members and other getters. It is a specific and unambiguous purpose.

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 description clearly implies the tool is used when you have a UUID and need a single member. It does not explicitly mention alternatives like list_members, but the context is clear for a simple getter, and no misleading guidance is given.

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