GlobalSource Partners MCP Server

read_research_post

Read-onlyIdempotent

Read a single published research post by post UUID.

Use this tool after calling search_research_posts and selecting the most relevant result.

The response includes post metadata, authors, sectors, body HTML, and a URL. Depending on the authenticated MCP user's permissions, the body HTML and URL may expose either the full research post or teaser content.

Missing, unpublished, and hidden-sector posts return a generic not-found error.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`post_uuid`	Yes	The stable UUID of the research post to read. Use a post_uuid returned by search_research_posts.

Output Schema

TableJSON Schema

Name	Required	Description
`post_url`	Yes	The URL where this research post can be viewed. This may be a full post URL or teaser URL depending on the MCP user's permissions.
`post_type`	Yes	The type of research post, e.g., 'Report', 'In Brief', 'Presentation', etc.
`post_uuid`	Yes	The stable UUID of the research post.
`post_title`	Yes	The title of the research post.
`post_authors`	Yes	The authors of this research post.
`post_sectors`	Yes	The sectors associated with this research post. Only clients who are permissioned for these sectors can access the full version of this post; other clients will receive teaser content.
`post_updated`	Yes	The most recent update timestamp of the research post in ISO 8601 format.
`post_body_html`	Yes	The HTML body available for this research post. This may be full post content or teaser content depending on the MCP user's permissions.
`post_published`	Yes	The publication timestamp of the research post in ISO 8601 format.
`post_snippet_notice`	Yes	A notice shown when the returned body contains only teaser or snippet content instead of the full research post. Null when the MCP user can view the full post.

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds valuable behavioral detail: response contents (metadata, authors, sectors, body HTML, URL), permission-dependent teaser vs full content, and generic not-found error for missing/unpublished/hidden-sector posts. This goes beyond what annotations convey.

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 short paragraphs, front-loaded with purpose, followed by usage flow, response summary, permission caveat, and error behavior. Every sentence contributes meaning without redundancy or fluff.

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 simple one-parameter read tool, the description covers the full context: how to select the UUID, what the response will contain, permission-based limitations, and error handling. No significant gaps remain.

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 only parameter post_uuid is fully described in the schema with the same guidance (use UUID from search_research_posts). The description adds no new semantic detail beyond repeating the schema. Baseline 3 for 100% schema coverage.

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?

The description opens with 'Read a single published research post by post UUID', which clearly specifies the verb, resource, and scope. It distinguishes from sibling tools by explicitly referencing search_research_posts and focusing solely on reading a post rather than authors or entities.

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?

Provides explicit when-to-use guidance: 'Use this tool after calling search_research_posts and selecting the most relevant result.' This directs the agent to a specific workflow and implies it is not for searching. Strongly differentiated from alternatives.

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

All GlobalSource Partners MCP Server tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0

Disambiguation5/5

Each tool targets a distinct resource and action: search entities by name, search posts by entity UUIDs, read a post by UUID, and read an author by UUID. The descriptions clearly delineate their purposes and include explicit cross-references, making misselection unlikely.

Naming Consistency5/5

All tool names follow a strict verb_noun pattern with a consistent 'research_' prefix: read_research_author, read_research_post, search_research_entities, search_research_posts. The verbs 'read' and 'search' accurately reflect retrieval operations, and naming is uniform.

Tool Count5/5

With 4 tools, the server is well-scoped for a read-only research retrieval domain. Each tool serves a necessary function in the entity-based research workflow, and the count is neither thin nor bloated.

Completeness5/5

The tool set covers the full research retrieval lifecycle: entity discovery (search_research_entities), content discovery (search_research_posts), and content retrieval (read_research_post, read_research_author). The dependency hints ensure agents can complete workflows without dead ends, and the read-only scope needs no CRUD operations.

Resources

Need Help?