Skip to main content
Glama

Get a UT Dallas club

club_get
Read-onlyIdempotent

Retrieve a UT Dallas student organization by club ID (not slug) to view its description, tags, contacts, officers, and update time; links are data only.

Instructions

Get a UTD club by its club ID (not slug): description, tags, contacts, officers and update time. Links are data only.

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": {
      "club_id": "<club_id>"
    },
    "name": "club_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
club_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior. The description adds useful context beyond that by naming the returned fields and stating 'Links are data only,' which tells the agent that links should not be treated as followable actions. It does not describe not-found or error behavior, but the annotations carry most of the safety profile.

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 compact sentence with the key identifier constraint front-loaded. The field list and link caveat are also concise. No wording appears redundant.

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 one-parameter read tool with rich safety annotations, the definition is mostly complete: it states the lookup key, distinguishes ID from slug, lists returned fields, and clarifies link handling. The main remaining gap is the absence of guidance on obtaining the club ID or handling not-found cases.

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 0%, so the description must clarify the single parameter. It does add meaningful semantics by saying 'club ID (not slug),' but it does not explain where to obtain an ID or give examples. The pattern and length constraints remain only in the schema.

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 states a specific verb and resource: get a UTD club by club ID. It also lists the data returned and clarifies that the identifier is a club ID, not a slug. It does not explicitly name the sibling search tool as the way to locate an ID, so it falls short of full sibling differentiation.

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 implied: use this when you already have a club ID. The parenthetical '(not slug)' helps avoid one misuse, but the description does not say when to use club_search instead or how to obtain a club ID. No explicit exclusions or alternatives are provided.

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