Skip to main content
Glama
Sign In
TypeWriter MCP

TypeWriter MCP

by yurchik228336
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

search_entries

Search all pages and entries for a given query to locate relevant storylines.

Instructions

Full-text search across all pages/entries.

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": {
      "query": "<query>"
    },
    "name": "search_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/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. It mentions the scope ('across all pages/entries') but does not disclose any other behavioral traits such as return format, pagination, case sensitivity, or read-only nature. Minimal additional context beyond the basic function.

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, concise sentence with no redundant phrasing. Every word contributes to the purpose and scope.

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 tool has no output schema and no annotations, so the description must explain what the search returns. It does not mention result format, whether it returns entries, pages, or both, or any limitations. While the scope is clear, the description is incomplete for a tool that returns search results.

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 coverage is 0%, so the description must compensate. The phrase 'Full-text search' implies that the 'query' parameter is the search text, adding some meaning beyond the empty schema description. However, it does not specify any format, wildcards, or options, so it only partially compensates.

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 clearly states the action ('Full-text search') and the resource ('across all pages/entries'), making it distinct from sibling tools like list_pages or add_entry. The scope is explicit and unambiguous.

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?

The description implies usage when a full-text search across pages/entries is needed, but it does not explicitly mention when to use this tool over alternatives such as list_pages or read_page. No exclusions or alternative comparisons are provided.

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