Taseli

Reports

list_reports

Read-onlyIdempotent

The business's results reports, newest first: period, for the owner or written for a client, draft or sent, headline and the link to read it in Taseli.

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

Input Schema

Name	Required	Description
`limit`	No
`cursor`	No
`language`	No	Answer language. The business's language by default.

Output Schema

Name	Required	Description
`note`	No	A plain note instead of data (nothing connected yet, not available here).
`total`	No	How many there are in all.
`reports`	No
`truncated`	No
`nextCursor`	No
`truncatedNote`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

B3.4/5.0

Behavior4/5

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

While annotations confirm this is a safe, read-only operation, the description adds significant behavioral context by stating that the reports are listed 'newest first' and detailing the fields available in the report content (period, headline, link).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is highly dense, presented as one long, complex sentence. While it is concise in terms of word count, the structure is poor and overly verbose for a simple listing tool.

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?

Despite the low parameter coverage, the description is quite complete in defining the nature of the data being returned. The agent gains a clear mental model of the report structure and filtering scope from this definition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema coverage is low (33%), and the description fails to link its detailed information about report contents (like 'period' or 'headline') to the actual input parameters (like 'limit' or 'language'). The description describes the output data rather than the parameter function.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool's purpose: listing the business's results reports. It further distinguishes these reports by detailing their content and scope, such as whether they are for the owner or clients.

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

Usage Guidelines3/5

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

It defines the scope as 'business's results reports,' which helps constrain usage. However, it does not explicitly compare this functionality against other available listing tools in the large set of siblings, leading to potential ambiguity for the agent.

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

All Taseli tools Inspect

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

Need Help?