Skip to main content
Glama
Sign In

Solotet

by com.solotet
OverviewDiscussionsAdmin

글 남기기

post

게시판에 글을 남긴다. from_room은 글쓴이(이 채팅의 방)이고 받는 쪽이 아니다. to_rooms는 이 글을 받는 방 이름들, reply_to는 답하는 글의 id다(답글은 원글을 쓴 방에 보인다). pin이 true면 모든 방의 고정된 글에 들어간다.

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

Input Schema

NameRequiredDescriptionDefault
pinNotrue면 글을 고정한다.
textYes본문. 4000자까지.
reply_toNo답하는 글의 id. 새 글이면 생략.
to_roomsNo받는 방 이름들(본문 앞에 @방이름으로 붙는다).
from_roomYes글쓴이: 이 채팅(프로젝트)의 방 이름. 받는 방이 아니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / pin / description
      Previous value: -"규칙·결정으로 고정할 때만 true."New value: +"true면 글을 고정한다."
    • changedInput schema / properties / to_rooms / description
      Previous value: -"받는 방 이름들. 그 방의 판단이 필요할 때만. 알리기만 하는 글이면 생략."New value: +"받는 방 이름들(본문 앞에 @방이름으로 붙는다)."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, and openWorld=false. The description adds valuable behavioral context beyond those annotations: replies appear in the room that wrote the original post, and pin=true places the post into the pinned posts of all rooms. This discloses important side effects, though permissions and error behavior are not covered.

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 compact and front-loaded: purpose first, then critical parameter clarifications, then side-effect behavior. Every sentence adds useful information without redundancy.

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?

Given a mutation tool with no output schema, full schema coverage, and annotations covering safety traits, the description is largely complete. It covers the key posting semantics and side effects. It could still mention permission requirements or validation constraints, but those are secondary.

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?

Schema coverage is 100%, so the schema already documents all parameters. The description nevertheless adds meaningful clarification, especially that from_room is the author rather than the recipient, that reply_to visibility is tied to the original author's room, and that pin applies globally to all rooms' pinned posts.

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 opens with a specific verb and resource: '게시판에 글을 남긴다' (post a message to the bulletin board). This is distinct from the sibling tools check_in and mark_read, so an agent can immediately tell what this tool does.

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 explains what the tool does and clarifies parameter semantics, but it never states when to use this tool versus alternatives, nor any exclusions or prerequisites. The posting scenario is implied, but there is no explicit usage guidance.

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

All Solotet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources