Skip to main content
Glama

Sense2 Promotional Products

get_company_facts

Read-only

Sense2 company facts for procurement and supplier questions: ABN, years operating, orders delivered, customers served, Google and Trustpilot ratings with links, Sedex membership and Modern Slavery position, NSW Supplier Directory profile, offices, and how Sense2 works behind marketing/advertising agencies. Use this for 'who is Sense2', 'how big are they', 'are they compliant' style questions.

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

Input Schema

NameRequiredDescriptionDefault
localeNoLocale: en-AU (default), en-US, en-NZ, de-DE, ja-JP — gates AU-only offers and localises the FAQsen-AU

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / locale
      Added value: +{
      +  "default": "en-AU",
      +  "description": "Locale: en-AU (default), en-US, en-NZ, de-DE, ja-JP — gates AU-only offers and localises the FAQs",
      +  "type": "string"
      +}
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally. The description adds valuable behavioral context beyond that by effectively documenting the returned content set, which matters because there is no output schema. It does not discuss freshness, sourcing, or any rate/auth considerations, but for a static read-only fact sheet that is a minor gap.

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 sentences: a dense but front-loaded content inventory followed by a usage clause. The long enumeration earns its place given the absent output schema, though it reads as a run-on list rather than a structured summary.

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-required-parameter, read-only lookup with no output schema, the description carries the return-value burden well by listing the fact categories and the question types it answers. Only the relationship to overlapping siblings (reviews, FAQ, why-Sense2) is left unspecified.

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?

The single locale parameter is fully documented in the schema (100% coverage), including default, allowed values, and effects on offers and FAQs. The description adds nothing about locale, so this is the standard baseline when the schema does all the work.

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 names a specific resource (Sense2 company facts) and enumerates the exact fields returned — ABN, years operating, orders delivered, customers served, ratings, Sedex membership, offices — so an agent knows precisely what it retrieves. It is clearly distinguishable from catalog/product siblings, though the ratings mention creates mild ambiguity with get_reviews and the 'how Sense2 works' clause overlaps get_why_sense2 without saying so.

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?

Provides explicit when-to-use framing via quoted example questions ('who is Sense2', 'how big are they', 'are they compliant') plus the caller persona (procurement and supplier questions). It stops short of naming when NOT to use it or which sibling covers overlapping ground such as reviews or FAQs.

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