Skip to main content
Glama

get_limits

Retrieve the full table of character and item count limits for Crack Story Builder so you can validate story or draft content before submission.

Instructions

크랙 스토리 빌더의 글자 수·개수 제한 전체 표.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and does little with it. The word '전체' (full/complete) implies the whole constraint set is returned without filtering, which is useful, but it never states that this is a pure read with no side effects, whether the values are static, or anything about the response shape. For a zero-annotation tool this leaves real gaps.

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?

A single short clause with no filler, and the key qualifier ('전체' – complete) is placed before the noun. Nothing could be removed without losing information.

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?

For a trivial zero-param lookup this is close to adequate, but with no output schema the description should signal what the table contains — which fields have limits (title, body, tags, etc.) and the unit of each limit. As written an agent knows the topic but not what it will receive.

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 for the description to disambiguate. Baseline 4 applies; the description does not misrepresent or contradict 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?

Names a concrete resource: the complete table of character-count and item-count limits for the story builder. The domain is unmistakable against siblings like get_story or save_story_draft, which operate on actual story content rather than constraints. It is a noun phrase with no verb, so it stops short of a top score.

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

Usage Guidelines3/5

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

There is no explicit when-to-use statement, no mention of checking limits before calling save_story_draft, and no exclusions. Usage is only implied by the content itself, which for a zero-parameter read lookup is reasonably self-evident but not spelled out.

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