Skip to main content
Glama

ProductNow

by ai.productnow
OverviewDiscussionsAdmin

search

Read-onlyIdempotent

Search the company's shared context — its intranet of documents, decisions, meeting notes, and synced systems — and return excerpts relevant to the user's question, with citations. Every source carries the document's id, title, and url; pass the id to fetch for the full text. Use this when the user's request depends on current information about their company, product, customers, team, or enterprise intranet. Covers ProductNow documents (PRDs, specs, RFCs, decisions) plus content synced from whichever sources the workspace has connected, e.g. GitHub, Jira, Linear, Salesforce, ServiceNow, Zendesk, Slack, Teams, Confluence, Notion, Google Drive, and meeting notes. Not for reading a known document in full (fetch) or listing a folder (fetch_folder). To find a folder by name, pass resultType folders. Pass query whenever the user names a topic, including when filters are also present. If the user asks only which documents match creator/date filters and names no topic, omit query to list documents by latest content edit; listing sources contain metadata but no excerpts. creatorNames matches document creators, not editors or contributors; its entries combine with OR, while creator and date filters combine with AND. Search workspace documents by default; use product_help only for questions about how ProductNow works. Pass folderId to limit workspace search to that folder and every folder nested under it; no results come from outside it. Omit folderId to search the whole workspace. Resolve the id with fetch_folder first. Ignored when searchScope is product_help. Pass resultType folders to search folder names instead of documents. Omit resultType to search documents. Folder results are name matches and include each folder's id, name, updatedAt, createdBy, isPrivate, parentFolderId when nested, and folderPath (the parent path) when it has a parent. They have no excerpts. A query is required. creatorNames and date filters apply to documents only. product_help cannot search folders. Topic-search results are relevance-filtered; all result sets are capped. Each source includes the document's folderId and folderPath when it is filed in a folder, and omits both when the document is at the warehouse root. Answer from the excerpts when possible, cite the documents you use, read a source document with fetch only when its excerpts are genuinely insufficient, and state uncertainty when evidence is weak or conflicting.

Input Schema

NameRequiredDescriptionDefault
queryNoThe question or topic to research in ProductNow knowledge. Omit (or pass an empty string) if the user didn't name one — see the tool description for what happens then.
folderIdNoLimit workspace search to this folder and its subfolders. Omit to search the whole workspace. Resolve the id with fetch_folder first. Applies to documents and, when resultType is folders, to folders. Ignored when searchScope is product_help.
resultTypeNoSet to folders to search folder names instead of documents. Omit to search documents. Folder search requires a query, ignores creatorNames and date filters, and does not apply when searchScope is product_help.
searchScopeNoSearch workspace documents by default, or use product_help to exclusively search ProductNow help documentation
creatorNamesNoRestrict results to documents created by one of these workspace users. Each entry is a name/email substring and may match several users; use a full email for precision. Entries combine with OR. Pass "me" for the calling user. If no entry resolves, the search returns no results. An empty list is treated the same as omitting this field.
updatedAfterNoRestrict results to documents whose latest active content edit is on or after this date (YYYY-MM-DD), interpreted as UTC. Compute this yourself for relative ranges like "the past 2 weeks". Omit for no lower bound.
updatedBeforeNoRestrict results to documents whose latest active content edit is on or before this date (YYYY-MM-DD), inclusive of the entire day (UTC). Must be on or after updatedAfter. Omit for no upper bound.

Output Schema

NameRequiredDescriptionDefault
queryYesNormalized query; empty means the tool used listing mode
foldersNoFolders whose names match the query, best match first. Present only when resultType is folders. Capped.
sourcesYesRelevant documents, capped by the tool's source limit
failedSourcesYesMatches whose fallback read failed; they remain in sources with evidenceSource unavailable. Empty when resultType is folders.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds genuinely new behavior: result sets are relevance-filtered and capped, listing sources carry metadata but no excerpts, folder results carry a specific field set, and folderId limits to nested subfolders. It also gives grounding instructions (answer from excerpts, cite, state uncertainty), which annotations cannot convey.

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

Conciseness2/5

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

The description is bloated and repetitive — 'Resolve the id with fetch_folder first. Ignored when searchScope is product_help.' appears near-verbatim twice, and folder/filter behavior is restated. It is also poorly front-loaded: the core routing guidance is buried under long enumeration of synced sources. Substantial trimming is warranted.

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 zero-required-parameter search tool with an output schema present, the description covers scope, result types, filter semantics, return shapes per result type, and how to consume results. An agent has everything needed to invoke and interpret it.

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 the schema already documents each parameter and the baseline is 3. The description goes beyond it by stating cross-parameter rules the schema does not: creatorNames entries combine with OR while creator and date filters combine with AND, and folder search ignores creatorNames and date filters. That added interaction logic justifies a step above baseline.

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 and resource ('Search the company's shared context ... return excerpts relevant to the user's question, with citations') and explicitly distinguishes itself from fetch and fetch_folder. An agent can tell it apart from every sibling without opening a schema.

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 explicit when-to-use ('user's request depends on current information about their company...'), when-not ('Not for reading a known document in full (fetch) or listing a folder (fetch_folder)'), and routes to the product_help alternative. The decision rules for query, folderId, and resultType are spelled out.

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

All ProductNow toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources