Skip to main content
Glama

list_expense_reports

Retrieve and filter expense reports from Odoo by status, with pagination controls for efficient management of expense sheets.

Instructions

    List expense reports (expense sheets).

    Args:
        state: Filter by state: draft, submit, approve, post, done, cancel (optional)
        limit: Maximum number of reports to return (default: 50)
        offset: Offset for pagination (default: 0)

    Returns:
        List of expense reports with their details
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateNo
limitNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions pagination behavior (limit/offset) and filtering by state, which is useful. However, it doesn't cover important aspects like authentication requirements, rate limits, error conditions, or whether this is a read-only operation (though 'List' implies read-only).

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?

The description is efficiently structured with a clear purpose statement followed by well-organized parameter explanations. Every sentence serves a specific purpose with zero waste, and the information is front-loaded appropriately.

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?

Given the tool's moderate complexity (3 parameters, no annotations, but has output schema), the description covers the essential functionality well. The output schema existence means the description doesn't need to detail return values. However, for a list operation with filtering and pagination, some additional context about default ordering or result structure would be helpful.

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?

With 0% schema description coverage, the description provides essential semantic information for all 3 parameters: 'state' filtering options (draft, submit, approve, post, done, cancel), 'limit' as maximum number of reports, and 'offset' for pagination. This compensates well for the schema's lack of descriptions, though it doesn't specify format constraints for the state parameter.

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 states the verb 'List' and resource 'expense reports (expense sheets)', making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'list_expenses' or 'list_expense_attachments', which would require more specific scope information.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives like 'list_expenses' or 'search_records'. The description only explains what the tool does, not when it's the appropriate choice among available options.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/industream/mcp-odoo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server