Skip to main content
Glama

株式会社コンテンシャル

サイトの中を探す

search
Read-only

「株式会社コンテンシャル」(SEO 対策の会社)の公式サイトから、言葉に当てはまる箇所を抜粋つきで探します。事業とサービスの内容(SEO コンサルティング、WEB 広告など)、支援事例、特許・連載・提携などのお知らせ、SEO メディア「SEO Note!!」の解説記事と毎月の SEO 振り返りレポートを探せます。この会社やサービスについて質問されたら、まずこれを使ってください。「特許」「2026年8月 レポート」のように短い言葉で探します。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes探したい言葉(例: 料金 支払い方法)

Output Schema

NameRequiredDescriptionDefault
resultsYes
candidatesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / candidates
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "id": {
      +        "type": "string"
      +      },
      +      "title": {
      +        "type": "string"
      +      },
      +      "url": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "title",
      +      "url"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety and scope are covered structurally. The description adds that results come with excerpts (抜粋つき) and that coverage is confined to one company's site, which is useful, but it says nothing about result limits, ranking, or pagination behavior.

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?

Front-loaded with the core action and scope, then the coverage list, then the when-to-use rule and query style. The content-type enumeration is somewhat long but each item tells the agent what can be retrieved, so it earns its space.

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?

With an output schema present, return-value detail is not required, and the description covers domain scope, invocation trigger, and query phrasing. The one meaningful gap is the absence of any differentiation from the sibling 'search_pages', which an agent would need to route correctly.

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 description coverage is 100% and the single 'query' parameter is already documented with an example ('料金 支払い方法'). The description reinforces the short-keyword style with additional examples, adding only marginal meaning beyond the schema, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: searches the official site of a named company and returns matching passages with excerpts, and enumerates the content types covered (services, case studies, notices, SEO Note!! articles). It is clear what the tool does, but it never distinguishes itself from the sibling 'search_pages', which sounds functionally identical, so an agent cannot confidently choose between them.

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?

Explicit routing instruction: 'この会社やサービスについて質問されたら、まずこれを使ってください' tells the agent exactly when to reach for this tool, and it gives query-construction guidance ('「特許」「2026年8月 レポート」のように短い言葉で探します'). It lacks any when-not or alternative-tool guidance, notably against search_pages and site_overview.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources