Skip to main content
Glama

cd_user

cd_user
Read-only

Look up a Chief Delphi user profile to check trust level, join date, team number, and bio, so you can judge how much weight to give that person's forum claims.

Instructions

Look up a Chief Delphi account profile: trust level, titles, join date, last seen, last posted, profile views, time read, badge count, location, website, bio and profile fields (FRC/FTC team number, rookie year, roles). Useful for judging how much weight to give a forum claim. Anonymous Discourse does not expose post counts or likes received, and it does not list that user posts — see the note in the output for why.

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": {
      "username": "<username>"
    },
    "name": "cd_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesAccount name exactly as it appears at the end of a profile URL (/u/<this>), with no leading @.
max_charsNoCap the reply at this many characters (default 20000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes further by disclosing scope limits — anonymous Discourse exposes no post counts or likes received, and the tool does not list that user's posts. Pointing the agent at a note in the output for the reason is useful behavioral context. It stops short of covering failure behavior for a nonexistent username or handling of case-sensitivity.

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 sentences, front-loaded with the action, then the payload contents, then the important limitations. The field parenthetical is dense but each item tells the agent what evidence is available; no sentence is 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?

For a two-parameter read-only lookup with no output schema, the description covers purpose, returned content, and known data gaps, which is nearly everything an agent needs. The only real omission is what happens when the username does not resolve to an account, leaving error handling unspecified.

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 100%, and the schema already explains that username must match the profile URL slug with no leading @, plus the max_chars default and bounds. The description adds nothing about either parameter, so it sits at the baseline where the schema does all the work.

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 and resource ('Look up a Chief Delphi account profile') and then enumerates the exact fields returned (trust level, titles, join date, badge count, FRC/FTC team number, etc.). This enumeration makes it unmistakable that the tool operates on a single user account, distinct from siblings like cd_topic, cd_categories, or cd_find which work on other resources.

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?

One clause gives a genuine when-to-use signal: 'Useful for judging how much weight to give a forum claim.' Beyond that there is no explicit routing guidance — no statement of when to prefer cd_find for locating a user or what to do when the username is unknown. Usage is implied rather than prescribed.

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