Skip to main content
Glama

Intakra Buying Signals and Workspace

Say what you sell

set_offering
DestructiveIdempotent

Use only after the user confirms the new text; call get_offering first to show what it replaces. Replaces what the workspace sells, in a sentence or two (for example "Payroll software for restaurant groups with 5 to 50 locations"). Intakra uses it to decide which findings become leads. It replaces the current description.

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": {
      "offering": "<offering>"
    },
    "name": "set_offering"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeringYesWhat you sell, 10 to 600 characters

Output Schema

NameRequiredDescriptionDefault
offeringYesWhat the workspace sells, as stored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "offering": {
      +      "description": "What the workspace sells, as stored.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "offering"
      +  ],
      +  "type": "object"
      +}
  2. Added
  3. Removed
  4. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the overwrite semantics are partly signaled. The description adds real context beyond that: what specifically gets replaced (the current description), the confirmation requirement, and the downstream consequence that Intakra uses this text to decide which findings become leads. Return format is not covered, but an 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the usage precondition, then purpose, then impact, which is the right order for a mutation tool. The closing sentence "It replaces the current description" restates the earlier replacement point and could be dropped without loss.

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

Completeness5/5

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

For a single-parameter mutation tool with full schema coverage and an output schema, the description covers everything an agent needs: when to call, what to call first, what the content should look like, and why the value matters downstream.

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?

Schema coverage is 100% and already specifies the 10 to 600 character bound, so the schema carries the mechanical constraints. The description goes further by showing a well-formed example and the framing ("a sentence or two"), which conveys the intended content shape rather than just the length limit.

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?

States a specific action and resource: it replaces what the workspace sells, written in a sentence or two, with a concrete example of the expected text. The read counterpart get_offering is named in the same breath, so an agent can immediately distinguish this write tool from that read tool.

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

Usage Guidelines5/5

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

Gives an explicit precondition (only after the user confirms the new text) and a required prior call (get_offering first to show what it replaces). This is exactly the sequencing an agent needs before overwriting a user-facing field.

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