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

scratch-unified-mcp

by blessed0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Social Set Whatimworkingon

social_set_whatimworkingon

Update your Scratch profile's "What I'm working on" status with a custom message up to 255 characters.

Instructions

Set the "What I'm working on" 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_whatimworkingon"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe new status. Max 255 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.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states that it sets a field. It does not disclose side effects, overwriting behavior, authentication requirements, or failure modes if no active session exists. The verb 'set' implies mutation, but that is minimal and not explicit enough for a tool without annotation support.

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?

The description is a single, front-loaded sentence that states the action with no filler. It is appropriately concise, though it lacks any structural enhancement or additional context.

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

Completeness2/5

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

The operation is simple, but the description omits the key prerequisite that an active session is required, leaving an agent without guidance on how to sequence this relative to social_set_active_session. The output schema covers return values, but this contextual gap prevents full completeness.

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%, and the schema already provides a thorough explanation of the `text` parameter, including max length and rejection behavior. The tool description adds nothing beyond the schema, so the baseline of 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') and names the exact resource ('What I'm working on' section on the active session's profile'). This clearly differentiates it from sibling tools like social_set_bio and social_set_pfp, making the intended action unmistakable.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that an active session must exist first (e.g., via social_set_active_session), nor any conditions that would favor this over social_set_bio or social_set_pfp. It is purely functional with no usage context.

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