WorkPick Press

検証済み企業プレスを検索

search_press

日本企業の検証済み・構造化済みプレスリリースを検索します（法人番号で企業を特定し、原本リンク付き）。各結果は法人番号(国税庁)と原本URLによる帰属(provenance)付き。Search verified, structured press releases from Japanese companies (company resolved via corporate number, original source linked). Every result carries provenance (corporate number + original source URL) so it can be cited and verified. category one of: funding(経営・資金調達), product(新商品・新サービス), partnership(事業提携・協業), hr(人事・組織), event(イベント・キャンペーン), report(調査・レポート), award(受賞・認定), store(店舗・施設).

Input Schema

TableJSON Schema

Name	Required	Description
`tag`	No	タグ（完全一致）
`limit`	No	最大件数（既定10, 上限50）
`query`	No	キーワード（headline/lead を部分一致）
`since`	No	この日時以降に公開（ISO8601, 例 2026-01-01）
`company`	No	企業名（部分一致）または法人番号13桁（完全一致）
`category`	No	カテゴリ: funding(経営・資金調達), product(新商品・新サービス), partnership(事業提携・協業), hr(人事・組織), event(イベント・キャンペーン), report(調査・レポート), award(受賞・認定), store(店舗・施設)

TDQS

A3.9/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It adds context about result provenance and verification, which helps the agent understand the tool's behavior. However, it does not explicitly state that the tool is read-only or have side effects, but searching is inherently read-only.

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

Conciseness4/5

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

The description is relatively concise with two English sentences and a category list. Bilingual content adds bloat but does not hinder understanding. Information 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?

No output schema exists, but the description explains what results contain (provenance). It covers the essential behavior for a search tool, though pagination or sorting details are missing. Sibling tools are mentioned implicitly by differentiation.

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%, so baseline is 3. The description does not add significant meaning beyond the schema's parameter descriptions. It provides context about the overall tool but not individual parameter semantics.

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 clearly states the tool searches for verified and structured press releases from Japanese companies, with provenance details. It distinguishes from siblings (get_press_article, list_company_press) by emphasizing search across multiple criteria.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for searching press releases but does not explicitly state when to use this tool over siblings or when not to use it. No guidance on exclusions or prerequisites.

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

All WorkPick Press 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/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: one retrieves a single article by slug, one lists all press for a company, and one searches across companies with category filters. No overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case: get_press_article, list_company_press, search_press. The naming is predictable and uniform.

Tool Count4/5

Three tools is slightly on the low side but appropriate for a focused read-only press retrieval server. The scope is narrow enough that each tool earns its place.

Completeness4/5

The set covers the core operations for retrieving verified press releases: single article, company listing, and search. Missing potential features like category listing or pagination metadata, but the main workflows are supported.

Resources

Need Help?