Skip to main content
Glama

PicPay MCP

by io.github.mcp-dir
OverviewAdmin

openfinance_get_item_status

Read-onlyIdempotent

Returns the current status of a bank connection (UPDATED, UPDATING, LOGIN_ERROR, etc.), its executionStatus, connector metadata, and a reconnect_url that reopens the widget in UPDATE mode for that connection (re-authenticate / enter MFA token in place, without disconnecting and without consuming a connection slot). Omit item to get the status of ALL linked banks at once (returns { count, items }); pass item for a single bank.

Bulk support: accepts item_ids for batched execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemNo
item_idNo
item_idsNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Changed2 schema fields changed
    • addedInput schema / properties / item_id
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / item_ids
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  6. Added
  7. Removed
  8. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The description adds valuable behavioral context beyond annotations: the reconnect_url reopens the widget in UPDATE mode without disconnecting or consuming a connection slot. It also explains bulk execution. Annotations (readOnlyHint, idempotentHint, destructiveHint) are consistent with the read-only nature of returning status.

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 paragraph that efficiently conveys key information. It is front-loaded with the main return fields and usage scenarios. A more structured format (e.g., bullet points) could improve scanability but is not essential.

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?

The description covers the return formats for both single and all banks, including fields like executionStatus and reconnect_url. Although there is no output schema, the explanation is sufficient for correct usage. Sibling tools provide more detailed data, so this tool's scope is well-defined.

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 coverage is 0%, so the description must explain parameters. It explains the effect of omitting `item` and passing `item`, and mentions `item_ids` for bulk. However, the difference between `item` and `item_id` is not clarified, leaving ambiguity about which identifier to use.

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

Purpose5/5

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

The description clearly states the tool returns the current status of a bank connection, including specific fields like executionStatus, connector metadata, and reconnect_url. It distinguishes between getting status for all banks (omit `item`) and a single bank (pass `item`), which differentiates it from sibling tools like `openfinance_list_connections`.

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

Usage Guidelines4/5

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

Clear guidance is provided on when to omit `item` (all banks) vs pass it (single bank), and bulk support via `item_ids` is mentioned. However, no explicit comparison to alternative tools (e.g., `openfinance_list_connections` vs this status tool) is given.

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

All PicPay MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources