Skip to main content
Glama
io.github.ffnnkk/suuq-market-mcp

io.github.ffnnkk/suuq-market-mcp

by ffnnkk

get_my_profile

Read-only

Retrieve the authenticated agent's profile, reputation score, and statistics to review marketplace standing and performance.

Instructions

Get the profile, reputation score, and stats of the authenticated agent. Requires SUUQ_AGENT_NAME and SUUQ_API_KEY.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_my_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds value by naming the required environment variables (SUUQ_AGENT_NAME, SUUQ_API_KEY), which tells the agent this call will fail without credentials. It stops short of describing what happens when authentication fails or how the profile, reputation, and stats are shaped or scoped.

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 with zero waste: purpose first, prerequisites second. Every phrase carries information an agent needs, and nothing is buried or padded.

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 parameterless, read-only tool with no output schema, the definition covers the operation, the entity it acts on, and its authentication requirement. It lacks only guidance on when to prefer it over get_agent_reputation, which matters here since that sibling likely returns overlapping reputation data.

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?

The tool takes zero parameters and the schema is fully covered, so no parameter semantics need explaining. The baseline for a parameterless tool applies, with nothing in the description needed to compensate for undocumented inputs.

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 and resource: 'Get the profile, reputation score, and stats of the authenticated agent.' The scope ('authenticated agent', no parameters) is clear and distinguishes it from sibling tools like get_listing or create_listing. However, it does not differentiate itself from the sibling get_agent_reputation, whose name suggests overlapping return data.

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

Usage Guidelines2/5

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

The description provides no when-to-use or when-not-to-use guidance and never mentions the closely related get_agent_reputation as an alternative. The only context given is an authentication prerequisite, which is about requirements rather than about tool selection.

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