Skip to main content
Glama
Offorte Proposal Software

Offorte Proposal Software

Official
by offorte

get_proposal_directories

Read-only

Retrieves proposal directories grouped by status—edit, open, won, lost, and closed—so you can find and manage proposals by workflow stage.

Instructions

Get all proposal directories grouped by status (edit, open, won, lost, closed)

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": "get_proposal_directories"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.1
  2. Removed
  3. Changed2 schema fields changedv1.0.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  4. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value by disclosing the return grouping and enumerating the five status buckets (edit, open, won, lost, closed). It stops short of describing what a directory record contains or whether results are paginated, which matters since no output schema exists.

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?

A single front-loaded sentence with the resource first and the grouping detail in parentheses. No filler, no restatement of the tool name, and the status enumeration is packed efficiently.

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

Completeness3/5

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

For a parameterless read-only listing this is close to adequate, and the status taxonomy is the key missing piece that it does supply. However, with no output schema the description is the only source of return-value information, and it never explains what a 'proposal directory' is or how the groups are shaped.

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

Parameters4/5

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

The tool takes zero parameters and the schema is an empty object with additionalProperties=false, so there is nothing for the description to disambiguate. Baseline 4 applies per the rules for parameterless tools.

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?

States a specific verb and resource (get proposal directories) plus the grouping dimension and the five status values. It is distinguishable from get_proposal_details and search_proposals at a glance, though the term 'directories' is left unexplained, so an agent can't be fully certain what entity is returned.

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?

The description gives no when-to-use guidance and does not mention the sibling tools search_proposals or get_proposal_details, which an agent could easily confuse with this one. Usage is only inferable from the 'get all' phrasing — there is no stated prerequisite, scope, or exclusion.

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