Skip to main content
Glama
Sign In
mcp-server-smallinvoice

mcp-server-smallinvoice

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_efforts

Read-only

Retrieve a list of efforts with optional filtering, full-text search, pagination, and selectable response fields for tailored results.

Instructions

Returns list of efforts

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_efforts"
  }
}

Input Schema

NameRequiredDescriptionDefault
withNoComma separated, optional keys that should be included in the response.
qNoValue for full text search
filterNoFilter expression (JSON)
limitNoLimits the number of items returned. Number in a range [1-200]
offsetNoOffset of the first item to return. The offset of the initial item is 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true, but the description adds no behavioral details beyond stating it returns a list. No mention of pagination, default result size, or filtering behavior, which are important for understanding the tool's operation.

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

Conciseness4/5

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

The description is a single sentence, concise and front-loaded. It is not verbose, though it could benefit from more detail without harming conciseness.

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

Completeness2/5

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

Given the presence of 5 parameters (filter, limit, offset, q, with) and no output schema, the description lacks essential context such as how filtering works, pagination behavior, and default values. It is incomplete for a list tool with these capabilities.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond what the schema provides for each 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 'Returns list of efforts' clearly states the tool's verb and resource. It is not a tautology and distinguishes from sibling tools like get_effort, but lacks scope details that would differentiate it from other list tools.

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 this tool vs alternatives. It does not mention when not to use, nor does it reference other tools like get_effort for specific records.

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

Deploy Server

Other Tools