Skip to main content
Glama

What Cuttr has learned about this member

get_profile
Read-only

This member's saved style notes, how their own posted videos did against their usual views (winners and misses), and their niche. Call it before planning any edit and apply it.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 main added value is enumerating what comes back and mandating application of the notes. It says nothing about behavior when a member has no saved notes or no posted videos (empty/new-member case), which matters for a tool meant to gate edit planning.

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?

A single sentence that front-loads the returned data and ends with the action instruction. No filler, though the nested parenthetical makes it slightly denser than necessary for a one-line definition.

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?

With zero parameters and no output schema, the description carries the burden of describing the return value, and it does so by enumerating the three content categories. The remaining gap is the empty/no-history case, which an agent would want to know before treating the profile as authoritative when planning an edit.

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?

The tool takes zero parameters, so the baseline is 4; however the description offers no clarification about implicit scoping (whose profile — presumably the current member) or whether any contextual selection is needed. Nothing is wrong, but nothing is added beyond the empty schema.

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?

The description names the concrete content returned: saved style notes, posted-video performance versus usual views (winners and misses), and niche. That is specific enough to distinguish it from siblings like get_skill or get_bundle. It lacks an explicit verb ('retrieve/get'), opening with a noun phrase instead, but the resource is unambiguous.

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?

It gives a clear call condition: 'Call it before planning any edit and apply it.' That is a real when-to-use instruction tied to a workflow step. It does not state when not to call it or name an alternative source of the same information, so it stops short of full routing guidance.

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