Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ctvnews_sections

Lists valid CTV News sections for headline queries, covering 12 national topics and 15 local newsrooms while excluding video, photo, weather, podcast, sponsored, and shopping hubs.

Instructions

Get CTV News sections. Lists the 27 CTV News sections accepted by ctvnews-headlines: 12 national topic sections such as canada, politics and sci-tech, and 15 local newsrooms such as toronto, calgary and atlantic. Video, photo, weather, podcast, sponsored and shopping hubs are not included.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does well: it discloses the exact count (27), the split (12 national vs 15 local), sample values, and what is deliberately omitted. It does not describe the response shape, but the enumerated scope makes the tool's behavior largely predictable.

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?

Three sentences, front-loaded with purpose, then scope, then exclusions. No filler; every clause adds discriminating information about what the list contains.

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?

There is no output schema, so the description must convey the return content, and it does via counts, examples, and exclusions. It stops short of describing the exact response format, which is a minor gap for a simple static-list tool.

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 no parameter semantics to clarify and the baseline of 4 applies. The description correctly implies a no-argument enumeration call.

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?

States a specific verb and resource ('Get CTV News sections') and immediately ties it to its consumer, ctvnews-headlines. It quantifies the resource (27 sections) and enumerates representative values, so an agent can distinguish it from sibling section tools without opening a 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?

Explicitly frames the output as 'the 27 CTV News sections accepted by `ctvnews-headlines`', which tells the agent exactly when to call it (to resolve valid section identifiers) and which sibling it feeds. It also states exclusions (video, photo, weather, podcast, sponsored, shopping hubs), giving clear when-not guidance.

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