Skip to main content
Glama
Offorte Proposal Software

Offorte Proposal Software

Official
by offorte

search_contact_organisations

Read-only

Find organisations in your Offorte contacts by entering a name. Use this search to locate the right company record before creating or sending proposals.

Instructions

Search for organisations by name in the contacts

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_contact_organisations"
  }
}

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.9/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 adds almost nothing: it does not say whether matching is substring, prefix, or exact, whether results are paginated or capped, or what an empty result looks like — key unknowns for a search tool.

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 with the resource and matching dimension front-loaded and no filler. It is efficient, though its brevity borders on under-specification.

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?

A one-parameter read-only search with no output schema needs little, and the description covers the core intent. It is still incomplete on match semantics and result limits, which an agent needs to call and interpret it correctly.

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% — the single 'search' parameter is typed as a bare string with no description. The description partially compensates by clarifying that the value is an organisation name rather than an ID, but it gives no syntax, length, or partial-match hints.

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 (search) and resource (organisations) and scopes it to matching by name within contacts, which implicitly separates it from search_contact_people. It is clear what the tool does, though it never explicitly names the sibling it differs from.

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?

No when-to-use guidance is given: nothing tells the agent when to pick this over search_contact_people, search_proposals, or get_contact_details. The only implicit signal is the word 'organisations' in the name and description.

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