mcp-freesound

Get user profile

get_user

Read-onlyIdempotent

Retrieve a Freesound user's public profile, including sound and pack counts, about text, and homepage, by supplying the username.

Instructions

Get the public profile of a Freesound user (number of sounds, packs, about text, home page).

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": "get_user"
  }
}

Input Schema

Name	Required	Description	Default
`username`	Yes	Freesound username.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuine value by previewing the returned fields (sound count, packs, about text, home page), which matters because there is no output schema. It says nothing about behavior for nonexistent users, rate limits, or whether private fields are excluded.

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?

One sentence, front-loaded with the verb and resource, with the returned fields tucked into a compact parenthetical. Every clause earns its place and nothing is 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 one-parameter read tool with rich annotations and no output schema, the description covers what it does and what comes back, which is enough to invoke it confidently. The missing piece is routing guidance among the many get_user_* and get_pack* siblings.

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?

There is a single required parameter with 100% schema description coverage, so the schema already carries the meaning. The description implies the identifier is a user, but adds no format, casing, or lookup-failure detail beyond "Freesound username" in the schema; baseline 3 is appropriate.

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 public profile of a Freesound user") and enumerates the profile fields returned, which implicitly separates it from get_user_sounds and get_user_packs. It never names those siblings explicitly, so the differentiation is inferential rather than stated.

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?

There is no when-to-use guidance: nothing says to call this for identity/profile metadata versus get_user_sounds for sound listings or get_user_packs for pack listings. The only guidance is what an agent can infer from the word "profile".

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

Deploy Server