GlobalSource Partners MCP Server

by com.globalsourcepartners

read_research_author

Read-onlyIdempotent

Read a single research author by author UUID.

Use this tool when a user wants profile details for a specific research author returned by another research tool.

The response includes author metadata, biography fields, profile URL, and visible sectors associated with the author.

Missing, inactive, non-author, and hidden-sector-only authors return a generic not-found error.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`author_uuid`	Yes	The stable UUID of the research author to read. Use an author_uuid returned by another research tool.

Output Schema

TableJSON Schema

Name	Required	Description
`author_name`	Yes	The display name of the research author.
`author_uuid`	Yes	The stable UUID of the research author.
`author_sectors`	Yes	The visible sectors associated with this research author.
`author_profile_url`	Yes	The URL where this research author's profile can be viewed.
`author_biography_html`	Yes	The research author's biography as HTML, if available.
`author_short_biography`	Yes	A short biography or role summary for the research author, if available.

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable context beyond this by listing response contents (metadata, biography, profile URL, visible sectors) and disclosing the generic not-found error for missing/inactive/non-author/hidden-sector cases. No contradiction with annotations.

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?

Four short, purposeful sentences with no redundancy. The first sentence states the core action, the second gives usage context, the third summarizes the response, and the fourth covers error behavior.

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?

The tool has a rich output schema, so return values need not be fully spelled out. The description ably covers key output categories and error conditions, and the single parameter is fully documented in the schema. With strong annotations, this is complete for the tool's complexity.

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?

Schema coverage is 100%, with the parameter description already explaining that author_uuid is a stable UUID from another research tool. The tool description reinforces this but adds no new semantics or format details beyond the schema, so baseline 3 is appropriate.

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 a specific verb+resource: 'Read a single research author by author UUID.' This clearly distinguishes it from sibling tools that read posts or search 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?

Explicitly states when to use: 'when a user wants profile details for a specific research author returned by another research tool.' This also implies the author_uuid comes from a sibling tool, providing clear context and an implicit exclusion of search tools for already-known UUIDs.

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?