Skip to main content
Glama

Niche of One Network

My OneWriter drafts

onewriter_drafts
Read-onlyIdempotent

Members. List your OneWriter drafts and folders on this account, search them, or read one by id. Long text: best shown to the user as a document or artifact.

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": "onewriter_drafts"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoRead this draft.
queryNoWords to find.
folderNoOnly this folder.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds two things the annotations cannot: the operation is scoped to "this account," and long draft text should be surfaced to the user as a document or artifact rather than inlined — a genuine output-handling trait.

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?

Two short sentences, front-loaded with the resource and the available modes, with no redundant restatement of the name. The opening "Members." fragment is terse to the point of being cryptic, which is the only blemish on otherwise tight structure.

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?

For a read-only tool with three optional parameters and no output schema, the description covers scope, access precondition, operating modes, and result presentation. Missing details are minor, such as result limits or pagination behavior when listing or searching.

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%, so the schema already explains id, query, and folder. The description's "read one by id," "search them," and "folders" loosely map to those parameters but add no syntax, format, or interaction detail beyond the schema. Baseline 3 applies.

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?

The description names a specific resource (OneWriter drafts and folders) and three concrete operations: list, search, and read by id. That verb set separates it from the write-side sibling save_to_onewriter without the agent having to guess. It stops short of explicitly naming an alternative, so it is clear but not maximally differentiated.

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 three modes (list, search, read by id) implicitly tell the agent which parameter shape to use, and the leading "Members." hints at an account-membership prerequisite. There is no explicit when-to-use versus when-not-to-use guidance and no named alternative for the write path, leaving routing largely inferential.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources