Fetch category headlines from a public TechCrunch feed by providing a section slug. Returns fresh JSON items for news monitoring, research, or content curation.
Get TechCrunch category headlines. Returns fresh headlines from one public TechCrunch category feed.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | TechCrunch category slug |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavior, but it only states that it returns fresh headlines. It does not mention read-only nature, authentication requirements, rate limits, pagination, or error behavior. While it is a simple GET-like tool, the lack of any behavioral detail beyond the output type is a significant gap.
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?
The description is a single, compact sentence with no filler. It clearly states the action and the result, making it efficient for an agent to parse. It could be improved by front-loading the category aspect, but it is already concise and well-structured.
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?
The tool has no output schema, and the description does not specify the return format (e.g., array of strings, objects with metadata), whether pagination exists, or any limitations. Given the lack of annotations and output schema, the description is insufficient for an agent to fully anticipate the tool's behavior and results.
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?
The schema provides 100% coverage with a description 'TechCrunch category slug' and an explicit enum list, so the schema already documents the parameter thoroughly. The description adds no additional meaning beyond confirming it is a 'category feed,' which is redundant. Baseline 3 is appropriate.
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?
The description states a clear verb+resource: 'Get TechCrunch category headlines' and adds specificity by mentioning 'one public TechCrunch category feed.' This differentiates it from siblings like techcrunch_article (which retrieves a single article) and techcrunch_news (likely general headlines) by emphasizing the category feed aspect.
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?
The description implies a specific use case (category-specific headlines) but does not explicitly mention alternatives or when not to use it. There is no guidance on choosing between this and techcrunch_sections or techcrunch_news, leaving the agent to infer the distinction from the name and description alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.