Skip to main content
Glama
Offorte Proposal Software

Offorte Proposal Software

Official
by offorte

search_proposals

Read-only

Search proposals by query to locate matching Offorte proposals for review or follow-up.

Instructions

Search for proposals by query

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": {
      "search": "<search>"
    },
    "name": "search_proposals"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchYes

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

C2.7/5.0
Behavior2/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. Beyond that the description says nothing: whether "query" is exact match, keyword, or full-text, whether results are ranked or capped, and whether matching covers titles, clients, or body content are all undisclosed.

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?

One short sentence, front-loaded with the verb and resource, with zero filler. Brevity here reflects under-specification rather than tight editing, but nothing is redundant.

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?

With no output schema and 0% parameter documentation, the description is the only place search semantics and result shape could be explained, and it explains neither. An agent can form a guess but cannot predict what it gets back or how to shape the query.

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

Parameters2/5

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

Schema coverage is 0% for the single `search` parameter, so the description must carry the burden. "By query" only restates the parameter name and adds no syntax, format, or matching-behavior detail that would tell an agent what string to supply.

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?

"Search for proposals by query" states a specific verb (search) and resource (proposals), so an agent knows the operation at a glance. It does not differentiate itself from siblings such as get_proposal_details, get_proposal_directories, or get_proposal_templates, so it falls short of a 5.

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?

There is no guidance about when to use this search versus get_proposal_details (fetch one known proposal) or get_proposal_directories (browse structure). The word "search" implies a lookup use case, but no condition, exclusion, or alternative is stated.

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