List the available Logpush fields for a specific dataset in a Cloudflare zone.
List the available Logpush fields for a specific dataset in a Cloudflare zone.
| Name | Required | Description | Default |
|---|---|---|---|
| zone_id | Yes | required,The ID of the zone | |
| dataset_id | Yes | required,The Logpush dataset ID (e.g. http_requests, firewall_events) |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description only repeats the list action. It does not state that the operation is read-only, whether authorization is required, whether results are paginated, or how the returned fields are structured.
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?
A single front-loaded sentence with no filler; the verb and scope are immediately clear.
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?
For a simple list tool with fully documented parameters, the description states what is returned and the required scope. However, with no annotations and no output schema, it leaves gaps around read-only safety, pagination, and how to distinguish this zone-scoped call from its account-scoped sibling.
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%, so both required parameters are fully documented in the schema; the description merely restates that a dataset and zone are needed. It adds no syntax, format, or constraint details beyond what the schema already provides.
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?
Specific verb 'List' and resource 'available Logpush fields' with the scoping qualifier 'for a specific dataset in a Cloudflare zone'. It implicitly separates this tool from the account-level sibling via the zone scope, but does not explicitly name or route to that alternative.
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?
No when-to-use, prerequisite, or alternative-tool guidance. The description implies you need a zone and dataset ID, but leaves the choice between this and the account-scoped sibling to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.