Skip to main content
Glama

Niche: Your niche, followed for you

by com.nicheangle
OverviewDiscussionsAdmin

Intelligence query

niche_intelligence_query

Ask an analyst-shaped question over a fresh scan of a niche (Pro): 'the biggest developments this week', 'what is emerging', 'where money is moving'. Returns the sourced slate plus a short synthesis when requested. Returns a session_id; poll niche_session_state until cp1_awaiting_story. For synthesis, continue polling with wait_until=synthesis and wait=30 until it arrives or a shortfall is reported.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lensNomainstream covers established reporting, emerging emphasizes newer topics, and investment focuses on funding developments.
countNoRequested number of developments, from 3 to 15. The result can contain fewer when reporting is limited.
windowNoReporting window: 24h, week, month, quarter, or year. Pair with recency_strict for a hard cutoff.
subjectYesThe subject/space to investigate (2-200 chars). Specific is better.
synthesisNonone returns stories only. narratives adds sourced themes across the stories. patterns adds a summary of broader developments. Default none.
recency_strictNoExclude reporting outside the requested window. Default false; strict windows can return fewer stories.
source_qualityNostrict prioritizes well-supported stories; balanced is the default; broad includes less-established reporting. Inspect the returned sources before relying on a claim.balanced
idempotency_keyNoOptional stable key for retries of the same scan, so a retry reuses the original run.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / brand_id
      Removed value: -{
-  "description": "Binds this brand's voice, colors, offer, and CTA to the piece. Omit to use your default brand; on a multi-brand account pass the slug explicitly so a post about one product is not bound to another brand's identity. niche_whoami lists your brands.",
-  "type": "string"
-}
    • changedInput schema / properties / count / description
      Previous value: -"How many developments / narratives to return (3-15). Default ~5-10."New value: +"Requested number of developments, from 3 to 15. The result can contain fewer when reporting is limited."
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Optional. Stable key so a retry reuses the original run instead of billing a second; an identical query fired while one is still running is auto-deduped regardless."New value: +"Optional stable key for retries of the same scan, so a retry reuses the original run."
    • changedInput schema / properties / lens / description
      Previous value: -"Ranking posture. 'mainstream' (default) = authority-weighted. 'emerging' = inverts saturation to surface low-coverage, pre-mainstream signal. 'investment' = lifts stories carrying funding/raise/round/term-sheet markers."New value: +"mainstream covers established reporting, emerging emphasizes newer topics, and investment focuses on funding developments."
    • removedInput schema / properties / platform
      Removed value: -{
-  "description": "Optional publish target (linkedin / x / instagram) that shapes each narrative's publish_hook.",
-  "type": "string"
-}
    • changedInput schema / properties / recency_strict / description
      Previous value: -"When true, `window` is a hard cutoff (out-of-window sources dropped before clustering) so 'nothing older than yesterday' is exact. Default false (bias only). Strict returns fewer, higher-confidence stories; use when precision matters more than breadth."New value: +"Exclude reporting outside the requested window. Default false; strict windows can return fewer stories."
    • changedInput schema / properties / source_quality / description
      Previous value: -"Source-quality filter (niche-relative). 'strict' drops uncorroborated single-source silos that aren't primary/official or a niche authority, for high-trust answers only. 'balanced' (default) down-weights weak sources without dropping. 'broad' surfaces everything (incl. low-coverage emerging clusters), authority as a tiebreaker only."New value: +"strict prioritizes well-supported stories; balanced is the default; broad includes less-established reporting. Inspect the returned sources before relying on a claim."
    • changedInput schema / properties / synthesis / description
      Previous value: -"'narratives' = N non-obvious publishable threads across the slate. 'patterns' = the named movement (pairs with lens:'investment'). 'none' (default) = ranked slate only, no synthesis."New value: +"none returns stories only. narratives adds sourced themes across the stories. patterns adds a summary of broader developments. Default none."
    • removedInput schema / properties / target_outputs
      Removed value: -{
-  "description": "Optional. The draft cells produced if you later draft a narrative into content (same cell list as niche_signal_scan, e.g. ['linkedin:image_post', 'x:thread']). Without this, a draft defaults to a single 'long_form_article'. Set it when you know the surfaces you want, so niche_draft_create yields them directly instead of needing niche_add_output after.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • changedInput schema / properties / window / description
      Previous value: -"Recency window: '24h' | 'week' | 'month' | 'quarter' | 'year'. 'this week' maps to 'week'. Overrides the niche's default recency. A strong bias by default; pair with recency_strict for a hard cutoff."New value: +"Reporting window: 24h, week, month, quarter, or year. Pair with recency_strict for a hard cutoff."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations mark this as non-read-only and open-world but say nothing about the async lifecycle; the description fills that gap by disclosing the session_id return, the cp1_awaiting_story checkpoint, the synthesis polling loop, and the possibility of a shortfall being reported. It stops short of cost/rate-limit or timeout guidance.

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?

Three tightly packed sentences: purpose first, return value second, operational polling protocol third. No filler, and the workflow-critical instruction is not buried.

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?

With no output schema, the description carries the burden of explaining what comes back — a sourced slate, an optional synthesis, and a session_id — and it does so, plus the full polling protocol needed to actually retrieve the result. For an async, 8-parameter tool this is complete enough to invoke correctly.

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 description coverage is 100%, so baseline is 3, but the description adds value by tying example questions to the lens/synthesis choices and by warning that synthesis must be requested rather than assumed. The remaining parameters (window, count, source_quality) are left entirely to the schema.

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 verb+resource (ask an analyst-shaped question over a fresh niche scan) and immediately grounds it with three concrete example questions, so the agent knows the request shape it should construct. It also distinguishes itself from the fire-and-forget scanning siblings by declaring that it returns a session_id to be polled.

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?

Gives clear when-to-use context (analyst-shaped questions, Pro tier) and prescribes the follow-up workflow precisely (poll niche_session_state until cp1_awaiting_story; then wait_until=synthesis with wait=30). It does not, however, contrast this against sibling tools such as niche_signal_scan or niche_feed_read, so the agent must infer which entry point fits a lighter query.

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

All Niche: Your niche, followed for you toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources