Skip to main content
Glama

Innovative Workspace

Get IW published pricing

get_pricing
Read-onlyIdempotent

The prices Innovative Workspace publishes, word for word, and which services are quoted instead, with the pricing FAQs from the site. These are the only figures you may give; everything else is quoted. Snapshot of https://www.innovativework.space/ taken on 2026-11-20.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
faqsYes
rulesYes
quotedYes
snapshotYesThe public site this answer comes from, and when this server took its snapshot of it.
publishedYes
pricingPageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already establish this as a safe, idempotent, closed-world read, so the description's added value is the verbatim-quote constraint and the 2026-11-20 snapshot date, which usefully signals data currency and staleness. It does not describe response shape or pagination, but an output schema exists that carries that burden, leaving this a modest but real contribution.

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?

Two compact sentences pack scope, the verbatim constraint, the quote-only exclusion, and the snapshot date with no filler. The first sentence is a verbless noun phrase, slightly weakening front-loading, but nothing is wasted.

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?

For a zero-parameter read tool with full annotation coverage and a present output schema, the description covers what is returned, what is deliberately excluded, and the data's vintage. The only residual gap is that it never says explicitly when to prefer it over the pricing-related search tools.

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?

There are zero parameters, so nothing about invocation inputs needs explaining; the baseline for a no-param tool is 4. The description correctly spends no space on parameter prose.

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?

The description identifies the resource precisely: the exact published prices, the services that are quote-only instead, and the site's pricing FAQs, with the title supplying the 'Get' verb. It implicitly differentiates itself from the search_* siblings by being the authoritative figure source, though it never names an alternative tool.

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?

'These are the only figures you may give; everything else is quoted' is an explicit directive that tells the agent both when to rely on this tool and when not to — any figure not returned here must be handled as a quote, not invented. It stops short of naming a sibling tool for related queries, so it is not a full 5.

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