Skip to main content
Glama

Get GBP Expert to-do list

get_gbp_expert_todo
Read-onlyIdempotent

The latest GBP Expert guided-audit findings for a profile as a to-do list (title, detail, field, priority) with the user's status for each (open, done, dismissed). Reads the last saved audit only; it does not run a new audit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "profile_id": "<profile_id>"
    },
    "name": "get_gbp_expert_todo"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_idYes
include_closedNoInclude items marked done or dismissed. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), so the description's added value is the staleness caveat: results reflect the last saved audit, not live computation. It also discloses the status vocabulary (open, done, dismissed), which explains what 'status' means in the payload.

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?

Two dense sentences with the result shape first and the key constraint front-loaded at the end. No filler, and every clause carries information an agent needs.

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?

With no output schema, the description usefully enumerates the returned fields and statuses, and it flags the saved-audit limitation. Only the profile_id scoping semantics remain unaddressed, which is minor for a two-parameter read tool.

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 50%: include_closed is documented in the schema, but profile_id has no description in either place and the description does not clarify that it scopes the audit results to one profile. The field list describes the response rather than the inputs, so parameter meaning is only marginally enhanced.

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?

Specific verb and resource: returns the latest GBP Expert guided-audit findings for a profile as a to-do list, and it enumerates the returned fields (title, detail, field, priority, status). The closing clause 'it does not run a new audit' separates it from any audit-generating behavior an agent might otherwise assume.

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?

The description clearly states the retrieval context (last saved audit only) and an explicit exclusion (no new audit is run). It does not name a sibling to use when a fresh audit is wanted, but the when-to-use condition itself is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources