Retrieve structured live-blog metadata and ordered BlogPosting updates from a canonical NDTV live-blog URL; regular article URLs are rejected.
Get structured updates from an NDTV live blog. Returns live-blog metadata and the ordered BlogPosting updates embedded in NDTV's public LiveBlogPosting JSON-LD. Regular article URLs are rejected.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical NDTV live-blog article URL |
Changes observed during successful MCP inspections.
v1.17.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and discloses key behavior: it returns live-blog metadata and ordered BlogPosting updates from public JSON-LD, and rejects regular article URLs. It does not cover auth, rate limits, or error handling, but the core read behavior is clear.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the core action, followed by return content and a rejection constraint. Every sentence earns its place with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, so the description must explain return values, and it does: metadata and ordered BlogPosting updates. Combined with the clear input constraint, it is complete for a simple one-parameter read tool, though more detail on the update structure could be added.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the single url parameter is already described as a 'Canonical NDTV live-blog article URL'. The description adds marginal value by reinforcing that regular article URLs are rejected, but the schema already conveys the live-blog constraint, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Get structured updates from an NDTV live blog') and distinguishes itself from regular article tools by noting that regular article URLs are rejected. It does not name the sibling ndtv_live_blogs, so sibling differentiation is incomplete.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides one exclusion criterion ('Regular article URLs are rejected'), which implies usage is limited to live blogs, but gives no explicit when-to-use guidance or mentions alternatives such as ndtv_live_blogs or ndtv_article.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.