Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

townhall_author

Read-only

Fetch a Townhall author's public profile and recent story links from a canonical author URL. Use townhall_article for one story or townhall_sections to browse sections.

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

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical townhall.com/author/<slug> URL; alternative to slug
slugNoAuthor slug, e.g. amy-curtis

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / slug / description
      Added value: +"Author slug, e.g. amy-curtis"
    • addedInput schema / properties / url / description
      Added value: +"Canonical townhall.com/author/<slug> URL; alternative to slug"
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and openness profile is covered. The description adds the content scope (profile plus recent story links) but nothing about pagination, result limits, or how many "recent" stories are returned. With annotations carrying the behavioral load, a 3 is appropriate.

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?

Two sentences, zero filler, with the core purpose front-loaded and the routing advice second. Every clause earns its place.

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?

A read-only, two-parameter lookup with an output schema and complete annotation coverage needs little more than purpose and routing, both of which are present. Slightly short of a 5 only because it says nothing about the volume or recency of the returned story links.

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 100%: both url and slug are documented, including that they are alternatives. The description only reinforces the URL form ("canonical author URL") and never mentions the slug option, so it adds little beyond the schema. Baseline 3 is correct when the schema does the work.

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 states a specific verb ("Fetch") and resource ("Townhall author's public profile and recent story links") plus the input basis ("canonical author URL"). It explicitly distinguishes itself from townhall_article and townhall_sections, so the agent can identify it without opening the schema.

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

Usage Guidelines5/5

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

It names two concrete alternatives and the condition that selects each: townhall_article for a single story, townhall_sections to browse sections. That implicitly excludes those cases from this tool, giving the agent a clear routing decision.

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

All Crawlora MCP 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