Skip to main content
Glama

Get product context

mynahcast_get_product_context
Read-onlyIdempotent

Read the brand's product context (what the product is, who it is for, proof, CTA, banned claims). Read this before drafting any post: write only from these facts, link the ctaUrl, and never make a claim listed in bannedClaims.

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": {
      "brandId": "<brandId>"
    },
    "name": "mynahcast_get_product_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandIdYes

Output Schema

NameRequiredDescriptionDefault
urlYes
proofYes
ctaUrlYes
brandIdYes
audienceYes
featuresYes
oneLinerYes
updatedAtYes
productNameYes
bannedClaimsYes
problemsSolvedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and a closed-world read, so the safety profile is fully covered. Beyond that, the description adds genuine behavioral value by describing what the payload constrains (facts to write from, ctaUrl to link, bannedClaims to avoid), which is context the annotations cannot convey. It does not cover freshness, caching, or what happens if a brand has no configured product context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Two sentences, no filler. The core action comes first, followed by the pre-drafting obligation, so the most decision-relevant content is front-loaded.

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?

An output schema exists, so return values need no prose, and the description covers purpose, timing, and post-read constraints. The only meaningful omission is any statement about brandId or what occurs when the brand lacks product context configured.

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?

There is one parameter and schema description coverage is 0%: brandId is never mentioned in the description. However, the schema itself is self-explanatory (uuid format with an explicit pattern), and a single required identifier on a getter is hard to misuse, so the gap is minor rather than disqualifying.

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?

Specific verb plus resource ("Read the brand's product context") with a parenthetical enumeration of the resource's contents (what the product is, audience, proof, CTA, banned claims). The enumeration distinguishes it from sibling getters like mynahcast_get_brand_voice and mynahcast_get_style without naming them.

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?

Explicitly states when to call it: "Read this before drafting any post." It also implicitly frames the usage boundary by telling the agent the downstream obligations (write only from these facts, link the ctaUrl, avoid bannedClaims). It stops short of naming a sibling alternative for cases where brand voice or style matters.

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