Skip to main content
Glama
vvitovec

ABRA Flexi MCP Server

by vvitovec

Search overdue items

search_overdue_items

Identify overdue receivables and payables with compact summaries. Filter by scope, partner, date, and limit results for efficient review.

Instructions

List overdue receivables or payables with compact report summaries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNo
limitNo
scopeNoall
offsetNo
companyNo
profileNo
partner_idNo
Behavior2/5

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

No annotations provided, and the description does not disclose any behavioral traits such as default sorting, pagination behavior, or whether the tool is read-only. Minimal transparency beyond the basic function.

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?

Single sentence is concise but lacks structure. No bullet points or logical flow. Could be improved while maintaining brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Description does not specify the return format, pagination limits, or how parameters interact. With 7 parameters, high schema coverage needed, but none provided. The tool cannot be confidently used without external documentation.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no explanation for any of the 7 parameters. The agent must infer parameter meanings solely from names, which is insufficient for complex parameters like 'date' and 'profile'.

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?

Description clearly states the action (list), resource (overdue receivables or payables), and output style (compact report summaries). It distinguishes from sibling tools that target non-overdue items or different entities.

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 on when to use or avoid this tool. While the scope is implied by 'overdue items', there is no comparison to sibling tools or prerequisites mentioned.

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/vvitovec/abra-flexi-mcp-server'

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