Skip to main content
Glama
Sign In
scratch-unified-mcp

scratch-unified-mcp

by blessed0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Social Set Bio

social_set_bio

Update the About me section on your active Scratch profile. Provide a bio up to 200 characters to replace the existing text.

Instructions

Set the 'About me' section on the active session's profile.

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": {
      "text": "<text>"
    },
    "name": "social_set_bio"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe new bio. Max 200 characters; longer values are rejected here because Scratch would silently discard them.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It identifies the mutation and the scoped target, but it does not state whether the existing bio is overwritten, what happens if no active session exists, or what errors or response are returned. For a one-field setter this is mostly transparent, but the description stays at the surface.

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?

The description is a single sentence with no filler, front-loading the verb and the target resource. Nothing present is wasted, and the structure makes the tool's purpose immediately scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one parameter) and an output schema exists, so return-value handling is covered. However, the active-session precondition is only implied, and the description never explains the relationship to sibling session-management tools. Adequate, but with a clear gap around the operational context.

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?

Schema description coverage is 100%; the text parameter is well documented with the 200-character limit and the reason longer values are rejected. The tool description itself adds no parameter-level meaning beyond that, so the baseline 3 is appropriate.

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?

The description uses a specific verb ('Set') plus a specific resource ('About me' section on the active session's profile). It is immediately distinguishable from sibling setters like social_set_pfp and social_set_whatimworkingon, so an agent can route to the correct tool without opening schemas.

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 or when-not-to-use guidance. The description does not contrast with related social setters, nor does it explain the prerequisite that an active session must exist or be selected (e.g., via social_set_active_session). The phrase 'active session' implies a precondition but never instructs the agent on it.

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

Deploy Server

Other Tools