Skip to main content
Glama

Search UT Dallas clubs

club_search
Read-onlyIdempotent

Find UTD student clubs and organizations by keyword, name, alias, or tag. Get ranked matches with IDs to retrieve full club details.

Instructions

Search UTD student clubs/organizations by keyword, name, alias or tag. Returns compact ranked matches and IDs for club_get.

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": {
      "query": "<query>"
    },
    "name": "club_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is fully covered. The description adds that results are 'compact ranked matches', which tells the agent ordering and payload shape, but it says nothing about pagination behavior despite a cursor parameter existing, nor about how ranking is determined.

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 tight sentences with zero filler; the capability statement comes first and the downstream-tool hint second, which is the right front-loading for a search tool.

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

Completeness3/5

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

There is no output schema, so the description's note about compact ranked matches and IDs is doing useful work. But for a search tool with a cursor-based result set and three undocumented parameters, the omission of pagination and result-count behavior leaves a meaningful gap for an agent planning multi-page retrieval.

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 carry the parameter burden. It does explain what 'query' matches against (keyword, name, alias, tag), but 'limit' and especially 'cursor' — a pagination token with a 512-char bound — are never mentioned in either place, leaving the agent to guess at paging semantics.

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?

States a specific verb (Search) plus the resource (UTD student clubs/organizations) and enumerates the match fields (keyword, name, alias, tag). It also distinguishes itself from the sibling club_get by framing its output as IDs to feed into that tool, so an agent can tell the two apart without opening either schema.

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 phrase 'Returns ... IDs for club_get' implicitly defines the discovery-then-fetch workflow, which is real usage guidance. However, it never states when NOT to use this tool (e.g., when you already know the club ID, go straight to club_get) or what to do if no matches are ranked.

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