List API actions exposed by OpenProject. Retrieve action IDs and URLs with pagination support.
List API actions exposed by OpenProject.
select fields: id, url (see server instructions for select's general semantics).
limit is capped at OPENPROJECT_MAX_PAGE_SIZE (default 50); pass the returned next_offset as the next call's offset to page past the cap.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| offset | No | ||
| select | No |
Changes observed during successful MCP inspections.
v0.4.0Input schema / properties / selectAdded value: +{
+ "anyOf": [
+ {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "title": "Select"
+}v0.3.7Input schema / additionalPropertiesAdded value: +falsev0.3.3v0.3.0v0.2.3Output schema / (root)Previous value: -{
- "$defs": {
- "ActionSummary": {
- "properties": {
- "description": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "title": "Description"
- },
- "id": {
- "title": "Id",
- "type": "string"
- },
- "modules": {
- "items": {
- "type": "string"
- },
- "title": "Modules",
- "type": "array"
- },
- "name": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "title": "Name"
- },
- "url": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "title": "Url"
- }
- },
- "required": [
- "id",
- "name",
- "description",
- "modules",
- "url"
- ],
- "title": "ActionSummary",
- "type": "object"
- }
- },
- "properties": {
- "count": {
- "title": "Count",
- "type": "integer"
- },
- "limit": {
- "title": "Limit",
- "type": "integer"
- },
- "next_offset": {
- "anyOf": [
- {
- "type": "integer"
- },
- {
- "type": "null"
- }
- ],
- "title": "Next Offset"
- },
- "offset": {
- "title": "Offset",
- "type": "integer"
- },
- "results": {
- "items": {
- "$ref": "#/$defs/ActionSummary"
- },
- "title": "Results",
- "type": "array"
- },
- "total": {
- "title": "Total",
- "type": "integer"
- },
- "truncated": {
- "title": "Truncated",
- "type": "boolean"
- }
- },
- "required": [
- "offset",
- "limit",
- "total",
- "count",
- "next_offset",
- "truncated",
- "results"
- ],
- "title": "ActionListResult",
- "type": "object"
-}New value: +nullv0.2.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It usefully discloses the page-size cap and the offset/next_offset paging contract, which is real behavioral context. But it omits read-only confirmation, permission/auth requirements, and any note on the shape or volume of returned actions.
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?
Three short sentences, front-loaded with the tool's purpose and then the pagination mechanics. Nothing redundant, though the phrasing is slightly terse rather than crisply structured.
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 3-parameter list tool with no output schema and no annotations, the description covers pagination and the select semantics adequately. It leaves gaps around what an 'action' object is and whether any permissions are needed, which the absent annotations would otherwise supply.
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 0%, so the description must compensate, and it does for the key parameters: it explains what `select` accepts (id, url) and points to server instructions for general semantics, and it documents `limit` via the page-size cap. `offset` is covered only indirectly through the next_offset paging hint, so it is not fully documented.
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?
States a specific verb and resource ('List API actions exposed by OpenProject'), which clearly distinguishes it from the other list_* siblings that enumerate different resources (types, statuses, roles). It is clear, though it does not explicitly name sibling alternatives to disambiguate.
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?
Provides concrete operational guidance on how to call it: the limit cap of OPENPROJECT_MAX_PAGE_SIZE (default 50) and the instruction to pass the returned next_offset as the next offset. However, it offers no guidance on when to use this tool versus the sibling list_* tools, nor any prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.