Skip to main content
Glama

Get my Knacco profile

knacco_get_profile
Read-only

Identify the authenticated Knacco account and its language before personalising a response. Returns id, name and locale; no account identifier is accepted as input. Requires openid and only reads the connected account. Use knacco_list_library for owned products; this tool does not return purchases or files.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
localeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new context beyond them: the required openid scope, the fact that the account is derived from authentication rather than input, and that only the connected account is read. It does not discuss error behavior, but that is minor for a zero-arg read.

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?

Three compact sentences, front-loaded with the purpose, then scope constraint, then the sibling routing. The clause listing id, name, and locale mildly duplicates the existing output schema, which is the only slight waste.

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 no-argument, read-only identity tool with annotations and an output schema already in place, the description covers purpose, prerequisites (openid), scope limits, and the nearest alternative. Nothing an agent needs to invoke it correctly is missing.

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?

With zero input parameters the baseline is 4, and the description reinforces this by stating "no account identifier is accepted as input," which prevents an agent from trying to pass a user id. That is real added meaning, though there is no parameter syntax left to clarify.

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 ("Identify the authenticated Knacco account and its language") and immediately names the return fields (id, name, locale). It also names the sibling knacco_list_library and what it does not cover, so an agent can separate the two without opening a schema.

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?

Gives an explicit usage trigger ("before personalising a response"), an explicit exclusion ("does not return purchases or files"), and routes the agent to the correct alternative (knacco_list_library) for owned products. Nothing about when to select this tool is 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