Skip to main content
Glama

plateau-candy

get_profile

Read-only

Get studio profile — what Plateau Candy does, expertise, team, and contact. Use this first to understand who Plateau Candy is; returns identity, expertise areas, clients and all contact channels.

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_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
cityYes
nameYes
contactYes
foundedYes
expertiseYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's marginal behavioral value is limited. It does disclose the shape of what comes back (identity, expertise areas, clients, contact channels), but an output schema exists, making that partly redundant, and it says nothing about auth needs, caching, or freshness of the profile data.

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?

Front-loaded with the core purpose and the 'use this first' cue in the opening clause, so an agent gets the actionable part immediately. The tail clause restates the earlier content list (expertise, team, contact vs. expertise areas, clients, contact channels) and could be trimmed without losing information.

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 zero-parameter, read-only profile tool with an output schema and annotations already supplied, the description covers everything an agent needs: what it returns, who it describes, and when to call it. Nothing material is missing given the low complexity.

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, so there is nothing to disambiguate; the baseline for a parameterless tool is 4. The description correctly implies a no-argument call and adds no misleading parameter hints.

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?

Names a specific verb and resource (get / studio profile) and enumerates the content domains it covers: expertise, team, contact. It identifies the subject entity by name (Plateau Candy) so an agent cannot confuse it with a generic profile fetcher, though it does not explicitly differentiate itself from siblings like get_capabilities or get_services that sound content-adjacent.

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

Usage Guidelines4/5

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

Gives explicit ordering guidance with 'Use this first to understand who Plateau Candy is', which tells the agent when this belongs early in a session. It stops short of any when-not guidance or a direct contrast with get_capabilities/get_services, leaving overlap resolution to the caller.

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