Skip to main content
Glama

Get a public author profile

get_user
Read-onlyIdempotent

Get the public profile of someone who published on GitDex: their display name and how many software records and requests they published. USE WHEN the user asks who submitted a record or what else that author published; then list the records with search_software (submitted_by) or search_requests (requested_by). NEEDS user_id, the submitted_by.id, owner.id or proposed_by.id of a record. NO side effects; public; no confirmation. Returns nothing private: no email or sign-in details. A display name proves no identity. Recovery: NOT_FOUND means the id is wrong; take it from a record.

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": {
      "user_id": "<user_id>"
    },
    "name": "get_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesUser ID (UUID) from a record's submitted_by.id, owner.id or proposed_by.id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, so the safety profile is covered structurally. The description still adds real behavioral context beyond that: it is public, requires no confirmation, and deliberately omits email and sign-in details, plus a caveat that a display name proves no identity. It adds a failure-mode note (NOT_FOUND means the id is wrong) but says nothing about rate limits or response shape beyond the two fields named.

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?

Six short sentences, each carrying a distinct payload: what it returns, when to use it, what to call next, what input it needs, its side-effect profile, and its privacy boundary. The highest-value facts (purpose and the USE WHEN routing) are front-loaded with zero filler.

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

Completeness5/5

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

For a single-parameter read tool with full schema coverage and rich annotations, this covers everything an agent needs: input source, return contents, privacy constraints, sibling routing, and error recovery. No output schema exists or is needed, since the description names the returned fields directly.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents the single user_id parameter and where to source it. The description reinforces and slightly extends this by listing all three source paths (submitted_by.id, owner.id, proposed_by.id) and, more usefully, ties the parameter to a recovery rule: on NOT_FOUND, re-derive the id from a record.

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 ('Get the public profile of someone who published on GitDex') and immediately scopes what is returned: display name plus counts of published software records and requests. This is clearly distinguishable from get_software, get_request, and the search_* siblings, which return records rather than authors.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit 'USE WHEN' trigger ('the user asks who submitted a record or what else that author published') and then names the follow-up tools and the exact parameters to continue with: search_software (submitted_by) and search_requests (requested_by). The alternatives and the conditions selecting them are spelled out rather than left to inference.

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