Skip to main content
Glama

get_profile

Read-onlyIdempotent

Retrieves a user's platform standing, including level, solved and unsolved counts by tag, and recent submissions; uses the linked account when no handle is provided.

Instructions

The user's standing on one platform: level, solved and unsolved counts per tag, and their most recent submissions. Without a handle, uses the one linked with link_account.

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": {
      "platform": "<platform>"
    },
    "name": "get_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleNo
platformYes
recent_submissionsNo

Output Schema

NameRequiredDescriptionDefault
handleYes
platformYes
solved_idsNo
limitationsNo
submissionsNo
level_summaryNo
solved_by_tagNo
rejections_publicNo
unsolved_attempts_by_tagNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.3.0
    • addedInput schema / properties / handle / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / handle / default
      Added value: +null
    • removedInput schema / properties / handle / type
      Removed value: -"string"
    • changedInput schema / required
      Previous value: -[
      -  "platform",
      -  "handle"
      -]New value: +[
      +  "platform"
      +]
    • addedOutput schema / $defs / Submission / properties / judged
      Added value: +{
      +  "default": true,
      +  "title": "Judged",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / rejections_public
      Added value: +{
      +  "default": false,
      +  "title": "Rejections Public",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changedv0.2.0
    • addedOutput schema / $defs / Problem / properties / source
      Added value: +{
      +  "default": "platform",
      +  "title": "Source",
      +  "type": "string"
      +}
  3. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds value beyond that: it discloses the returned content and the implicit fallback behavior that the tool resolves the handle from the linked account. It does not say what happens if no account is linked, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loaded with the resource and payload before the handle fallback caveat. No filler or repeated phrasing. The line-wrapped formatting is slightly awkward, but nothing needs trimming.

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?

An output schema exists, so return values need not be spelled out, though the description helpfully summarizes them. For a tool whose only required parameter is platform, the omission of valid platform values, which is presumably sourced from list_platforms, and of failure behavior when no account is linked leaves an agent with real gaps.

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 carries the full burden. It explains handle semantics (optional, falls back to the linked account), but it never explains what platform values are accepted, even though platform is the one required parameter, nor does it connect recent_submissions to how many recent entries are returned or mention the default of 20 and the maximum of 500.

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?

States a specific verb-resource pair: it retrieves a user's standing on one platform, and it enumerates the payload (level, per-tag solved/unsolved counts, recent submissions). That is far more concrete than the name alone. It does not explicitly distinguish itself from possibly overlapping siblings like progress or show_dashboard, so it falls short of a 5.

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?

"Without a handle, uses the one linked with link_account" is genuine usage guidance for the optional-handle case, since it tells the agent it can omit the handle. However, there is no guidance on when to prefer this tool over progress or show_dashboard, nor any prerequisite such as needing an account linked first. Usage is implied rather than fully specified.

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